Skip to content

A small set of specifications, one shared product model

Intentset separates product meaning from implementation architecture and platform choices. Adopt the Core model on its own, or connect it to traceable vertical slices.

Core Specification v0.2

Draft intentset/core/0.2 · revision 2026-11-15

The product model: what a repository records about a product, from its purpose and outcomes down to each behavior and rule, how those records link to verification, evidence and the explanations readers are given, and how each moves from draft to released.

Read Core

Traceable Vertical Slice Architecture Specification v0.2

Draft intentset/vsa/0.2 · revision 2026-11-12

How code is organized around what the product does: each behavior has one owning slice of the codebase, a slice exposes a declared public surface and depends only on what it declares, and verification shows it delivers what it claims.

Read Traceable VSA

TypeScript + AWS Amplify Gen 2 Reference Profile v0.2

Draft intentset/typescript-amplify-gen2/0.2 · revision 2026-10-21

Traceable VSA in a TypeScript and AWS Amplify Gen 2 repository: where slices live, which imports intentset architecture check refuses, how a slice owns its backend resources, and areas for a backend too large for one CloudFormation stack.

Read the reference profile

Publishing, export and lists

Publication Profile v0.2

Draft intentset/publication/0.2 · revision 2026-11-15

How reviewed explanations become documentation and in-app help for one audience and release: what a request must name, what it may include and what stays withheld, the provenance each document keeps, and when an explanation needs review again.

Read the publication profile

Export Contract v0.6

Draft intentset/export/0.6 · revision 2026-11-14

The JSON a repository hands to other tools: the graph with its outcomes and measures, optional evidence, knowledge, impact and ownership reports, what is withheld, and what a consumer must check before importing it. Valid and deliberately invalid envelopes for testing a consumer ship with the conformance suite.

Read the export contract

List Contract v0.1

Draft intentset/list/0.1 · revision 2026-11-14

How a tool answers which records match: a closed selector of fields combined with AND and values with OR, a link looked at one hop away, records a withheld link leaves undetermined rather than guessed, and the result intentset list writes, the same from a repository or from its export.

Read the list contract

What conformance means

A conformance report names its scope, snapshot, specification version, checks, and exceptions. Linked evidence is not the same as passing evidence, and passing tests do not prove every documented promise correct.

The cases every check is held to are published as data, for implementations that are not this one. See the conformance suite.

Note

All six documents are drafts, each with a dated revision. Core §1 says what a change to them means, and the changelog records every one. The TypeScript reference implementation implements them, and its conformance suite is published for other implementations. The reference toolchain is at 0.16.0 on npm.