Tags
Six axes, none of them the theme axis. Themes say what area a kit serves; these say what it works on, how it works, what can go wrong with it, and who it is for.
Stanhopea tigrina, plate 7, Augusta Innes Withers; lithographed by Maxim Gauci, 1837–1843. Missouri Botanical Garden. Public domain. Credits
29 tags across 6 axes · 0 of 29 in use · 0 of 9 kits tagged
Every tag is reserved
The vocabulary is registered; none of it is in use. Each tag has a permanent address so it can be linked and cited now, and each will carry kits when the first kit leaves placeholder status. A tag turns active only when it can truthfully assert membership — the build fails if an active tag has no members, or a reserved one has any.
Artifact — what a kit works on
The material a kit reads or writes. Factual, and orthogonal to the venture theme — a kit in narrative and fundraising may work on a pitch narrative and a financial model at once.
- Venture record 0 of 9 Kits that read or write the shared record of company facts — the single substrate of assumptions, decisions and evidence that other kits consume instead of copying. artifact:venture-record
- Market evidence 0 of 9 Kits that operate on collected market material: competitor pages, industry reports, pricing sheets, signal feeds. The evidence set is the thing being processed, not the conclusion drawn from it. artifact:market-evidence
- Financial model 0 of 9 Kits that read or write unit economics, runway projections or budget spreadsheets — structured numbers whose assumptions must stay visible beside their outputs. artifact:financial-model
- Customer interview 0 of 9 Kits that work on discovery material captured as speech — interviews, call notes, support threads — where the unit of analysis is an utterance rather than a row. artifact:customer-interview
- Pitch narrative 0 of 9 Kits that read or write the venture story: deck prose, plan documents, investor updates. A single narrative under active revision rather than a published record. artifact:pitch-narrative
- CRM records 0 of 9 Kits that operate on pipeline rows — contacts, stages, follow-ups — where every write must be reversible and every deletion suspect. artifact:crm-records
- Web property 0 of 9 Kits that read or write the venture’s public surfaces: site pages, metadata, launch checklists, rollback plans. artifact:web-property
- Media asset 0 of 9 Kits that operate on demo and promo material — captures, cuts, audio, captions — where rights and provenance travel with every file. artifact:media-asset
Method — how a kit works
The machinery a kit uses to do its job. Factual. Says how, never how well.
- Structured search 0 of 9 The kit issues queries against a defined source with recorded parameters, so that the same search can be run again and compared. Coverage is bounded and the bound is declared. method:structured-search
- Field extraction 0 of 9 The kit pulls named fields out of unstructured or semi-structured material into a schema, leaving a trace from every extracted value back to where it came from. method:field-extraction
- Cross-reference check 0 of 9 The kit compares a claim against the source attached to it and reports agreement, disagreement, or an inability to check. Resolution failure is a result, not an error. method:cross-reference-check
- Schema validation 0 of 9 The kit tests material against a declared shape and fails loudly on violation, rather than coercing the material into the shape and continuing quietly. method:schema-validation
- Comparison and diff 0 of 9 The kit puts two versions of the same object side by side and reports what changed, including changes that are easy to miss by reading. method:comparison-diff
- Monte Carlo simulation 0 of 9 The kit reports a distribution of outcomes rather than a single confident number, with every sampled assumption recorded so the run can be reproduced. method:monte-carlo-simulation
- Drafting with citation 0 of 9 The kit writes prose in which every substantive claim carries a source that resolves. Drafting without that constraint is a different method and does not belong here. method:drafting-with-citation
Risk — what can go wrong
The failure mode a founder must watch for when running this kit. An editorial axis, and the one this registry exists for: a kit that cannot name its risk has not been inspected.
- Fabricated citation 0 of 9 The kit can name a source that does not exist, or attach a real source to a claim it does not make. The check is resolution: every reference must resolve to a retrievable record. risk:fabricated-citation
- Silent omission 0 of 9 The kit can drop material without saying so — a truncated result set, a skipped competitor, a filtered segment — leaving output that looks complete and is not. risk:silent-omission
- Claim overreach 0 of 9 The kit can state a conclusion stronger than its evidence supports, most often by dropping the qualifier that made the original claim defensible. risk:claim-overreach
- Stale source 0 of 9 The kit can rely on market material that has since changed — a pivoted competitor, a repriced product, a dead link — and present it as current without checking recency. risk:stale-source
- Irreproducible run 0 of 9 The kit can produce a result that a second run does not reproduce, because a parameter, a seed, a source version, or an ordering was never recorded. risk:irreproducible-run
- Confidential material 0 of 9 The kit can be pointed at customer data, term sheets or material under NDA, and produce output that leaks it. Consent and confidentiality travel with the material. risk:confidential-material
- Unauthorized outreach 0 of 9 The kit can contact real people or write to live systems without an explicit human gate — the failure mode of any sales or launch automation left unattended. risk:unauthorized-outreach
Audience — who it is for
Who the kit is aimed at. Editorial, and deliberately coarse — a kit may carry several.
- Solo founder 0 of 9 Aimed at someone running the whole venture alone, with more urgency than budget, who needs the working steps visible rather than abstracted away. audience:solo-founder
- Founding team 0 of 9 Aimed at a small team splitting the work, where the kit’s output must be legible to a co-founder who did not run it. audience:founding-team
- Early operator 0 of 9 Aimed at the first hires who inherit a founder’s workflow, and need to see what was checked and what was not before relying on it. audience:early-operator
- Technical co-founder 0 of 9 Aimed at someone who will read the kit as software — its inputs, its failure modes, its determinism — and expects it to behave like a tool rather than a conversation. audience:technical-cofounder
- Student founder 0 of 9 Aimed at someone building inside a course or program, where the kit doubles as teaching material and its failure mode must be safe to demonstrate. audience:student-founder
Curated — the curator’s own marks
Hand-maintained editorial assertions by the operator. There is deliberately no sync script for any tag in this namespace.
- Reference kit 0 of 9 The operator considers this kit the clearest worked example of what the review standard asks for, and points at it when explaining the standard to someone new. curated:reference-kit
- Teaching example 0 of 9 The operator uses this kit when teaching, because its failure mode is easy to demonstrate and easy for a student to reason about. curated:teaching-example
Batch — publication cohorts
Publication cohorts (batch:<yyyy>-w<ww>) — the freshness axis. Registered and empty; the first record is minted when the first kit reaches Declared.
This axis is registered and has no tags yet. The first is minted when the first kit reaches Declared.
The axes that are not tags
Two axes are stored fields on the record rather than tags, because each kit has exactly one value for them. They are linked here for one-stop discovery.
- Theme — the research area a kit serves, with its coverage disposition.
- Lifecycle state — Placeholder, Declared, Evidenced, Reviewed. See how it works.