5 specifications, 44 requirements. All libraries
Requirement Mechanism Who Note FR-001check bun run verifysuite/layers.test.ts: every file of the real tree is in a unit and no import is outside its row FR-002check bun run verifysuite/layers.test.ts: verify runs every check of the library
Requirement Mechanism Who Note FR-001check bun run verifysuite/vocabulary.test.ts: every list has one registry entry for each case and each entry is a member of the ontology plan:, and a value outside a list is an error value FR-002check bun run verifysuite/fold.test.ts: an item of each kind has the fields of the core and the five states FR-003check bun run verifysuite/ids.test.ts: the smart constructors, the clock over the real merge clock of anyfs, the sight of an id and the refusal of a far-future id FR-004check bun run verifysuite/actors.test.ts: the actor rules in the types and in the constructors, from the values of a file and from a run's context FR-005check bun run verifysuite/events.test.ts: an event of each type, deeply frozen, with the refusals of makeEvent FR-006check bun run verifysuite/fold.test.ts: the fold is the same for any order and any repeat, the conflicts, the proposals and the authority of each field FR-007check bun run verifysuite/links.test.ts: a link that closes a cycle of blocks is refused with its items FR-008check bun run verifysuite/typing.test.ts: the governance and logical sources import no system module, read no clock and use no random source FR-009check bun run verifysuite/typing.test.ts: the sources hold no any, non-null assertion, enum or cast but brand, and the files that must not compile do not (ts-expect-error, held by the compiler of verify) FR-010check bun run verifysuite/legacy-ids.test.ts: the id of a ULID against its layout, the id of another scheme, and the actors of a file by the rule of the configuration FR-011check bun run verifysuite/records.test.ts: the files of events and items round-trip with their keys in order and decode totally, and the monorepo's three records round-trip as written
Requirement Mechanism Who Note FR-001check bun run verifysuite/reconcile.test.ts: an item seen in two places has a trace for each with the content last taken and the record as read FR-002check bun run verifysuite/reconcile.test.ts: the classes new, unchanged, updated and absent, and no event from an unchanged place, over generated places FR-003check bun run verifysuite/reconcile.test.ts: the match order anchor, external id, fingerprint, locator, a single match for an item, and the ids of a new item FR-004check bun run verifysuite/reconcile.test.ts: the three-way merge as events of a tool, the conflict value naming the three values, labels merged, parent of links FR-005check bun run verifysuite/reconcile.test.ts: a derived close, its reopening, and the person's event winning FR-006check bun run verifysuite/reconcile.test.ts: the history a place keeps is taken as it is, by union of ids, and an id with other content is a conflict FR-007check bun run verifysuite/patches.test.ts: proposals of same as in a fixed order, nothing merged, a linked pair not proposed again FR-008check bun run verifysuite/patches.test.ts: a patch around one event with the operation its type says, refused with no target FR-009check bun run verifysuite/patches.test.ts: the capability of each patch, append event, the outbox naming the capability and the entries offered again FR-010check bun run verifysuite/patches.test.ts: a dry run with no hash, the plan of the hash applied and any other hash refused FR-011check bun run verifysuite/views.test.ts: the query over items, events, links and traces, and proposals not counted unless told FR-012check bun run verifysuite/views.test.ts: the roadmap, the graph of blocks, the matrix of requirement by item and responsibility FR-013check bun run verifysuite/views.test.ts: the matrix of what a source holds with its findings, and Markdown and JSON5 saying what they cannot hold FR-014check bun run verifysuite/typing.test.ts: the governance and logical sources are pure and hold no any, non-null assertion, enum or cast but brand
Requirement Mechanism Who Note FR-001check bun run verifysuite/store.test.ts: one file for each event, total loading, the clock after every id and the union of two stores in any order FR-002check bun run verifysuite/sources.test.ts: defineSource and its refusals FR-003check bun run verifysuite/sources.test.ts and suite/markdown.test.ts: an explicit target, a dry run, a hash that is not the plan's refused, the outbox FR-004check bun run verifysuite/markdown.test.ts, comments.test.ts, issues.test.ts, event-files.test.ts: the laws of a lens over generated places, and a source that breaks them found FR-005check bun run verifysuite/sources.test.ts: the same source over memory, a folder and SQLite, and a write that finds the file changed a conflict FR-006check bun run verifysuite/issues.test.ts: the real issues folder of commons/data, every field kept, the barrel checked, the status replaced alone FR-007check bun run verifysuite/event-files.test.ts: made-up files of the monorepo's schema read, found, and written with the bytes kept; the comparison with the monorepo's fold is skipped and says why FR-008check bun run verifysuite/markdown.test.ts: the examples of the task list section of GFM, the marker rules, nesting, the one-character write FR-009check bun run verifysuite/comments.test.ts: the markers, the fingerprint that survives a move, the anchor, generated and vendored files FR-010check bun run verifysuite/sources.test.ts: a real temporary Git repository for the commits and a local fake of the host's client; no account, so the live client is left untested FR-011check bun run verifysuite/sources.test.ts: the reserved names, the matrix of every source, and a journal of the real Evidence Capture code that no source reads or changes
Requirement Mechanism Who Note FR-001check bun run verifysuite/planctl.test.ts: definePlanning, the one reader and the field it names for each wrong value FR-002check bun run verifysuite/planctl.test.ts: the principal by session, argument and configuration, and the refusal that says none is established FR-003check bun run verifysuite/planctl.test.ts: the verbs over a made-up repository in process and as a real process, the dry run, the hash and the check status FR-004check bun run verifysuite/planctl.test.ts: the tool server over its real transport with an agent and its principal, human-only options refused and an agent that cannot confirm FR-005check bun run verifysuite/planctl.test.ts: only the file at the root, JSON not read, a trust recorded by the person and lost when the file changes FR-006check bun run verifysuite/planctl.test.ts: planctl render prints the items in the formats and says what Markdown cannot hold