Planning Quality: 6 tests: 6 passed, 0 failed, 0 skipped, 3 of 44 requirements proved, 0 open issues, 0 open tickets. The tests and issues of the libraryPlanning: its three layers as namespaces, and the records at the boundary, which are of the logical layer.#Entry pointssrc/mod.tssrc/governance/mod.tssrc/logical/mod.tssrc/logical/records/mod.tssrc/physical/mod.ts#Modulesgovernance/modThe Governance layer of Planning: what an item is and what may happen to it, as data and types (commons 0037-planning FR-001 to FR-007): the closed lists, time and ids, actors with their principals,…governance/brandThe one place a brand is put on a value: a smart constructor checks a value and then calls brand, so that an id, an instant or a day exists only as the result of its constructor.governance/vocabThe closed lists of Planning, each a union of literals with one registry entry for each case (commons 0037-planning FR-002, FR-041).governance/timeThe time of an event and the day a deferral ends, as branded text made only by a parser: an instant is YYYY-MM-DDTHH:MM:SSZ in UTC to the second (0037-planning FR-003) and a day is YYYY-MM-DD;…governance/idsThe ids of Planning: an item id and an event id are each a UUID version 7 as 36 lower case characters (RFC 9562 section 5.7), branded and made only by a smart constructor that returns a Result…governance/actorThe actor of an event: a person, an agent or a tool (0037-planning FR-005).governance/eventThe events of an item (0037-planning FR-003): each one case of the closed union of fourteen types, with an id, the item it is of, a time and an actor, and the data its source wrote.governance/itemAn item and what is folded from its events (0037-planning FR-001, FR-004): a sum of the kinds of item over one shared core, a state that is never stored as a fact, the links, the comments, the…governance/observationWhat a source read (0037-planning FR-008, FR-009, FR-046): an observation is one thing read in one place, with where it was read (a locator), the SHA-256 of the bytes it was read from, a fingerprint…governance/patchA patch (0037-planning FR-010): one event for one explicit source and place, in a closed union of the operations add an item, add an event, change a state, link and confirm.logical/modThe Logical layer of Planning: the model it reasons with (commons 0037-planning FR-003 to FR-007, FR-044): the fold of events into an item, the cycle check of links, the clock that makes ids and the…logical/canonicalThe canonical text of a value: its properties sorted by name, recursively, and its arrays in their order (the order of RFC 8785 section 3.2.3 for the keys), with a property whose value is undefined…logical/clockThe ids of an item and of an event are made by the hybrid clock of AnyFS's merge, reused and not made again (0037-planning FR-007): nextTime and seeTime choose the time of the next id, and…logical/foldThe state of an item is the result of fold, a pure and total function from the events of the item (0037-planning FR-004): events are taken in the order of their id (a UUID version 7 sorts as text…logical/legacy-idThe ids of a record read from another scheme (0037-planning FR-044).logical/linksThe links between items and the rule that the links of kind blocks make a graph with no cycle (0037-planning FR-009): a link that would close a cycle is refused with the items of the cycle named.logical/reconcilereconcile (0037-planning FR-016 to FR-018): what a source read, brought together with the store.logical/previewThe plan of a patch and its preview (0037-planning FR-011, FR-032): a plan is what a source would write to carry a patch out, effect by effect (a target, the revision it expects, the text it makes…logical/outboxThe outbox (0037-planning FR-014, FR-033): a patch is applied only to a source that declares the capability it needs; for any other it is an outbox entry that names the capability, or the reason the…logical/duplicatesLikely duplicates (0037-planning FR-019): a similarity of the titles, bodies and places of two counted items (the overlap of their lower-cased words, with a share for the same place), and for each…logical/queryThe query algebra (0037-planning FR-020): a typed, pure and read-only question over the items, events, links and traces (select, filter by state, kind, label, assignee, severity and origin, join,…logical/viewsThe views of Planning (0037-planning FR-021): pure functions of the items.logical/matrixThe matrix of what each source can hold (0037-planning FR-015): each field of an item ends, for each source, expressed (the place holds it), carried (it travels in a form the place keeps) or…logical/configThe configuration of Planning (0037-planning FR-037, FR-045): a typed value a repository writes in planning.config.ts with definePlanning (the identity, as defineConfig of repoctl is), and…logical/itemsThe items of a set of events: each item's events folded under a policy, with the events whose histories are not one item named.logical/records/modThe records Planning reads and writes at its boundary (0037-planning FR-025, FR-038): its own files of events and items in JSON5, and the issue files, event objects and summaries of the monorepo,…logical/records/ergaThe records of the monorepo's issues, read and written as they are (0037-planning FR-025, inventory entries 1 and 2): an issue file, erga/issue@1, a JSON5 text of an issue's events with a leading…logical/records/erga-readAn issue file of the monorepo read as an item with its events (0037-planning FR-025, FR-044, FR-046): each ULID or other id becomes an id of the library by the pure function of FR-044 and is carried…logical/records/erga-indexThe summary of a work's issues in the monorepo's form, erga/issues-index@1, made from items (0037-planning FR-039, inventory entry 2): a rendition, a pure function from items to a value that…logical/records/storeThe files of a store and of a published edition (0037-planning FR-038), in JSON5, which the library encodes and decodes at its boundary with the codec of formats.logical/records/renderRendering items in a format (0037-planning FR-039): a pure function from items to text, Markdown or JSON5, that says what its format cannot hold and does not drop it silently.logical/records/trace-fileThe files of a store that are not events: a trace of an item in a source (the content last taken, the base of a three-way merge) and an entry of the outbox (a patch no source could apply, and why),…physical/modThe Physical layer of Planning: what reads files, runs programs and reaches the network (commons 0037-planning phases 2, 4, 5 and 6): the store of events over AnyFS, the port a source implements, the…physical/sourceWhat a source is (0037-planning FR-013, FR-030, FR-032): a typed lens over one kind of place with a name, its capabilities and a place; acquire reads the place and returns its observations and…physical/storeThe store of events over an AnyFS store (0037-planning FR-007, FR-038): one file for each event at <item>/<event>.json5, the traces of the sources under .traces/ and the outbox under .outbox/.physical/conformanceThe laws of a lens as a check a source is given (0037-planning FR-023, FR-042): checkLens returns the laws a source breaks.physical/catalogWhat the sources of Planning are, as data (0037-planning FR-015, FR-031, FR-046, FR-047): the names of the sources built and of the sources reserved for the later phase (a source of the list is not…physical/file-sourceA source over the files of an AnyFS store (0037-planning FR-029): it is written against a store that has read, write, list and cas, so the same source works over a folder, Git, S3, SSH, SQL or memory.physical/sources/markdownThe source for Markdown (0037-planning FR-026): each task list item of GitHub Flavored Markdown 0.29-gfm section 5.3 is an item.physical/sources/commentsThe source for comments in source files (0037-planning FR-027): a comment that carries one of the markers set in the configuration (TODO, FIXME, XXX and HACK by default, the markers the…physical/sources/issuesThe source for the typed issues of a library (0037-planning FR-024): the folder issues/ as data 0044-issues FR-002 lays it out, one NNNNN-slug.ts for each issue, listed in order by mod.ts.physical/sources/event-filesThe source for a folder of event files (0037-planning FR-025): each JSON5 issue file of the monorepo's schema erga/issue@1, together with the event objects of its store (erga/issue-event@1) of…physical/sources/githostThe source for a Git host (0037-planning FR-028): the issues of a repository and the references of its commits, read through a client of the Git host contract of githost and never one of its own.physical/worldWhat the program works on (0037-planning FR-037, FR-045, plan.md Trust): the configuration file read, the store opened and the sources made from the configuration.physical/collectCollecting (0037-planning FR-016, FR-034): each source of the configuration is read, reconciled with what the store holds and, where the run is to write, the events and traces are written.physical/planctlThe program planctl as Headless' tree (0037-planning FR-032, FR-034, FR-035; commons headless 0003-headless-output, 0010-audience-tiers, 0013-mcp-surface): the verbs collect, show, query,…