Jevelopers is the neatHack 2026 team building TicketStub, a keepsake studio for the nights people want to remember. The product vision connects event research, editable artwork, exact ticket typography and a digital or printed keepsake.
Keep the night: turn a ticket into a stub worth framing.
Development status — 12 October 2026: the studio preview and component implementations are on their owning repositories' default branches. Local tests and historical sponsor receipts cover specific slices; the integrated release gate remains blocked. This page introduces the design and repository map. It does not certify an available physical product, a completed checkout or a passing end-to-end release.
Explore the studio source · Download the public source collection · Acceptance checklist · Contribute
The design starts with an event link or search, then offers research, style selection and tactile interactions. The illustration shows that intended journey. Research and creative outputs must retain source references, uncertainty and review boundaries; the studio documentation and component READMEs explain the implemented paths and their remaining integration work.
The studio design includes five editions. These images are design references, and each edition has its own palette and type within the stub system. They are not supplier samples or evidence of available print finishes.
 Classic thermal box office |
 Letterpress inked and pressed |
 Risograph two inks, overprinted |
 Minimal one number, lots of air |
 Researched art made from the facts |
 |
Research informs the picture. This Glasgow illustration shows how a confirmed fact, such as rain, can guide an art brief. It is an example, not a verified event record. The imagery guidance calls for a text-free art layer, with event names and dates set separately by the composition system. Generated output still needs review; a prompt does not guarantee accuracy. Rules: imagery.md |
 Foil reference: a visual direction for light-responsive digital effects |
 Holo reference: material inspiration, not an approved supplier option |
 Back-of-stub concept: notes, companions and a link to the memory |
The current brand sources describe paper and foil treatments, with app-versus-marketing direction still under brand review. Browser support, reduced-motion behavior, audio settings and physical production capabilities belong to their implementation owners. Consult the application README for current pricing modes and checkout configuration; these reference images make no price, shipping or print-availability promise.
The public directory below was checked on 12 October 2026. Repository READMEs are the entry points for setup and current limitations; a source repository's existence does not establish an accepted deployment or integration.
| Repository | Owns | Current scope |
|---|---|---|
| getticketstub.com | Customer studio, project and order authorization, application integration, architecture | Preview application and verification tooling; consult its runtime and provider configuration |
| brand-kit | Master identity, logo sources, tokens and usage guidance | Source assets and local checks; identity and distribution approvals remain pending |
| landing-page-repo | Product-page source and its reviewable deployment artifact | Static page and local validation; application adoption and deployment evidence are separate |
| marketing-material | Messaging, collateral, demo narrative and claim provenance | Versioned internal drafts and review records; publication needs its own approval |
| team-dashboard | Typed admin Finance views and application-facing UI adapter | React module and synthetic conformance evidence; actual host acceptance remains separate |
| Repository | Owns | Current scope |
|---|---|---|
| agent-harness | Durable workflows, decision ports, checkpoints, recovery and trace delivery | Local runtime and scoped provider evidence; host and full-workflow readiness tracked separately |
| event-intelligence | Event research, sourced facts, provenance and research cache | Bounded research implementation and local verification |
| creative-engine | Creative briefs, generated artwork and immutable design revisions | Creative API and local validation; configured providers and consumer acceptance have separate gates |
| print-production | Exact typography, composition, preflight and production artifacts | Local renderer and production API candidates; supplier and integrated release acceptance pending |
| fulfillment-connectors | Provider quotes, submission identities and status observations | Connector and policy implementation; genuine provider authorization and evidence remain gated |
| cost-intelligence | Usage, prices, budgets, ledger, reconciliation and financial reporting | Local Finance implementation; source pins, hosted persistence and consumer evidence govern integration |
| Repository | Owns | Current scope |
|---|---|---|
| shared-contracts | Cross-repository contract design and compatibility ownership | Offline receipt and proposal validators on main; the canonical package candidates remain unmerged |
| integration-evals | Master acceptance checklist, evaluation runners and evidence index | Executable checks and scoped historical sponsor evidence; full release gate remains blocked |
| .github | This profile, contribution guidance and shared templates | Reduced governance-guidance scope accepted; repository settings and downstream adoption remain separate |
Jevelopers-GetTicketStub.com-Submission collects public default-branch source snapshots for convenient review. Its manifest records the exact source commits. Develop components in their owning repositories; the generated copies are a snapshot, not a new integrated build or a product acceptance receipt.
The application owns the customer project and purchase authorization. The runtime repositories provide workflow execution, event facts, artwork, production files and provider observations; cost-intelligence owns the financial records, and team-dashboard presents authorized projections. Shared-contracts owns the interface design and compatibility handoffs, while integration-evals owns the acceptance decision.
Use the canonical architecture guide, maintained contract catalog and implementation plan for the detailed map. Proposed interfaces, private development archives and accepted releases are different states; each consumer records its own exact pin and verification.
 Timothy Wayne Gregg @CompleteDotTech |
 Lars van der Zande @lmvdz |
 Zachary Wright @zwright8 |
 @lajefahemp-collab |
TicketStub is our project for neatHack 2026. The master acceptance checklist records qualified historical owner acceptance for the three sponsor criteria: Neatlogs traces, Entire checkpoints and the CFO.ai business plan. Each receipt retains its tested revision, original capture context and limitations.
Those sponsor receipts do not establish a fresh integrated product run, universal trace coverage, current deployment, generic Finance-export acceptance or a completed submission. The evidence index and release gate carry those distinctions.
Want to help, or to review? Start with the contribution guidance and the acceptance checklist.
Brand, editions and studio design by @lmvdz
Reference images are AI-generated explorations, with no vendor, artist or venue marks
Type: Fraunces and Inter Tight (SIL OFL 1.1)