Skip to content

Changelog

Every version of the executable with the decisions it carried, the changes in its commit range and the artifacts it published — composed by the release subsystem, never written by hand.

A release is a record of the layer, not a file somebody edits after the fact. majordomus generate changelog reads those records, pairs each one with the decisions dated inside its window and the commits in its range, and writes the result as one value in three encodings — docs/generated/changelog.json for a program, .yaml beside it, .md for a reader. This page is a fourth projection of the same value, so it cannot say anything the tool does not.

What that buys: a version cannot appear here without a release record, a change cannot appear without a commit that carries it, and an artifact cannot appear without the record's own evidence for it — the file name and the SHA-256 the record read off the file it published.

provenance
current version
0.4.0
document
majordomus/changelog/v1
projected from
docs/generated/changelog.json
for a reader
docs/generated/changelog.md
the same value, elsewhere

The Cockpit runs it from the capability page above; Swagger UI runs the route, on the server this repository starts. None of the four is written down twice — they are projections of one declaration.

v0.3.1

0.3.12026-09-0845f921efb1511 change(s) 19 decision(s) 6 artifact(s)

Decisions

The architecture decisions the layer dates inside this version's window, each with the route the document records for it.

Release on GitHub →Compare →Tree at this version →

Changes

Every commit in this version's range that parses as a conventional commit, under the heading its type carries; a subject that parses as nothing is grouped as other.

# Added feat 188
# Fixed fix 171
  • distribution the release builds on runners that still exist98772ecbf
  • ui the audit follows the topology, and finds the pages it was missing0151eaa20
  • distribution the advertised install command is proved against the published sitee574d800b
  • ci the Pages workflow triggers on the paths the gate model now names99af7b927
  • discovery the in-process glob matches bracket expressions, so the ADRs are indexed621303ad5
  • test case 76 says why it failed, and follows the schema path rule6b4da355d
  • rust the four rustdoc errors that fail the gate on every branch48299b76f
  • ci the baseline is named where the tool writes it, and the merge driver is declared onced3a36fd25
  • bench a refusal is a measurement, and only a failure stops the runcd836a67e
  • distribution the release archive carries the launcher the MCP one execs5213b79dc
  • why a repository without a catalogue still has a case for every route434437f00
  • ci rustdoc builds under -D warnings, and two cases read the surfaces as they are served0dd8c4ace
  • site the shared moment card on the audience and area pages, and a command note that folds71dd7bd00
  • site long code tokens fold on a phone instead of pushing the page sidewaysdd5164556
  • usecase a recorded scenario says nothing the clock decides711035897
  • ci every gate green after the topology landeda60b65e04
  • ci no example path names a home directory, and the merge driver is wired relative to the worktree46f55ef8f
  • worktree a session's scratch checkout is never cleanup-eligibledb9a5a349
  • ci the runner's clone wires the merge driver it is checked for5a190b041
  • rust the three lints that fail the gate, written the way clippy asks6864d4a5c
  • ci the runner's clone wires the merge driver it is checked for62334ee59
  • rust the three lints that fail the gate, written the way clippy asks5c749b262
  • site the web dataset carries the site's own version, and a description is not a path4c1884e1b
  • claims,test three claim pages the contract rejects, and a rule that fired on a file27af381df
  • release one entry per path in a release archive4db957624
  • git an agent's worktree is not part of this repository8967a8b49
  • generate a plan writes inside the repository it was planned forde76ee617
  • schema four component names that meant two things each, and one ADR number claimed twice58b552932
  • generate a plan writes inside the repository it was planned for6fdfdc4db
  • site the published contract path points at a file that existsfbbf668e5
  • release publication regenerates every projection of the record77681eeac
  • distribution the public release metadata says it is generated2d83344c8
  • generate one definition of a repository-relative path, and the projections it makes reproduciblef3be42bca
  • tests the fixture's own declaration had grown past its size limit623970e9b
  • ci a home directory in an authored document fails where it was written0873947de
    I0908 A hosted process has no repository, and says so instead of failing
  • web a declared surface that was never built keeps its mount, and the tree is regenerated2c3be37c9
  • plan an issue's reasoning stops naming a developer's home directory138840b40
    I0908 A hosted process has no repository, and says so instead of failing
  • examples the walk-through stops naming a directory that no longer exists059f04a90
  • generate a generated artifact names its schema by a path, not by this machinee0a5e71f0
  • generate a provenance banner names the repository, not the machine3d99a94cc
  • ci one declaration per plan output, so the workflow parses at all9f0fe56cb
  • ui the audit reaches zero, and stops attributing its own failures to pages2ca03db97
  • capture capture render repairs the archive it is named to repair5ba6d4c52
  • capture the provider sanitiser took over the rendering's field readera7610c142
  • integration the defects the merged tree's own gates foundb43b0b5ce
  • deploy the deployment schema takes the identity master's loader requires1fb7cca3b
  • ci the Cockpit probe gets the libraries it probes forb99d84822
  • schema the context contract keeps its constraints where they are now declared61016a9ba
  • ci satisfy the gates the branch had not been run through76a71048f
  • context a directory's contract is discovered because it is onebe874eef8
  • site the published session projection says nothing true only of its readerbdd150c55
  • test an allow-list is a banner and then patternsdcfef63cb
  • site a skill example's path is a path, so it wraps like one40e8c430b
  • ci the Cockpit job probes pages whose libraries it never built7b76530dd
  • ci the three things the first CI run found5ff8036a6
  • ci the Cockpit probe gets the libraries it probes forf992a15af
  • adr 0017 uses the heading levels the validator requires973dbc711
  • ci the Cockpit gate is declared, selected, and never ran1ce4d09dc
  • usecase the commit a handover quotes, not only the one it states7014e7c4f
  • usecase a derived record states its commit in prose, and evidence must notd28a771ac
  • ci one cockpit_assets output, not two0b64ef18e
  • derive a quoted section kept its words and lost its paragraphsadb949968
  • ci three gates that were not gating anything4667e9245
  • site the generator converges in one passb4fde1f59
  • site a generated document's page is projected from what the run producedd93ba2bd9
  • schema the context contract keeps its constraints where they are now declared1c8af6b72
  • ci satisfy the gates the branch had not been run through4044f0181
  • context a directory's contract is discovered because it is onee65a47cf4
  • ci satisfy the gates the branch had not been run throughc73c52fc1
  • site a skill example's path is a path, so it wraps like one2b42014b5
  • ci the Cockpit job probes pages whose libraries it never builta6dfd8c86
  • ci the three things the first CI run found3ffbbad55
  • usecase the commit a handover quotes, not only the one it states18f6e1d47
  • usecase a derived record states its commit in prose, and evidence must not05919656e
  • context a directory's contract is discovered because it is onedb9906cf3
  • ci one cockpit_assets output, not twoef0400a91
  • docs the use-case example nests its fences, and the capture example uses no real home994561f73
  • derive a quoted section kept its words and lost its paragraphsa9dbdf927
  • ci three gates that were not gating anything504126f84
  • evidence the EPIPE diagnostic in recorded output, at its source and in the normaliser7719c72d1
  • rules one assertion that runs, in whichever form the author chooses19fb3b56d
  • usecase the run's verdict is a fact about the run, not about its printing5ea1db0f4
  • evidence the recorded evidence carried the operating system's user name0241fbff5
  • usecase the run's verdict is a fact about the run, not about its printing1742142d4
  • ci the plan job never declared cockpit_assets, so that gate could not fire2b6447d3c
  • schemas the session-record schema joins the convention, and the tree is regeneratedf17cd99c0
  • session the four ways the session subsystem was already inconsistent with itselfa840487c3
  • web the declaration module asserts what it wires, and an error names its kind onceeb38d9207
  • rules the reserved names are held by tests, not by a runtime finding9dea53fdb
  • capture,state no eval in the writer, and current.yaml declares the key it writesa7fb5a6c9
  • schemas the capture and document schemas join the one convention2751b3950
  • web the listing header is a format string, not four arguments762cd61c3
  • adr renumber the scenario decision to 0014b872ba2f5
  • bench a capability module called `system` vanished from three denominatorsaf56e2e3f
  • site two assertions that moved with the tree under them7f3d9b96b
  • layer the checks the last three kinds left behindc38bd83c8
  • site route the documents a run writes before it writes thema1ba27a7c
  • pages the derived content is committed, so the fast path can render a clone4f98d412c
  • site a command page's breadcrumb names the command it is underdcb596c79
  • site a command page names the whole command, and says its summary once8b038698e
  • usecase pin the scenario repository branchfafd4acb8
  • claims the scope claim carries its own note02af4b255
  • site a new selection clears the previous one's edges; Registry is listed once in the navigationc9a173590
  • site the core-model diagram sits in the section's width, beside its callouta7d5847bd
  • site the homepage README fragments link site routes, not repository paths37dd48266
  • site a new selection clears the previous one's edges; Registry is listed once in the navigation8059b4fca
  • site a long identifier wraps instead of widening a registry or section pageb3ceaf6e3
  • site a description on the executable's pages wraps at 320pxc53b8f0dd
  • usecase the evidence normaliser masks the verification wall time969696df3
  • site the executable's route slug follows Zola, one Registry page3e8dac549
  • usecase the scratch directories are named as the no-forbidden-constructs case reads thema974d2c31
  • bench the routes bench loads the scope the index builder now takesb32dcdeb1
  • bench the routes bench loads the scope the index builder now takes144771d09
  • scope migrate seeds the scope, knowledge reads it, case 65 ignores the budget line94cdec334
  • bench the routes bench loads the scope the index builder now takes9454c0e4c
  • scope migrate seeds the scope, knowledge reads it, case 65 ignores the budget line1fce6f281
  • bench a baseline fails a run only on the host that recorded it38dedb392
  • plan the model accessors and the status JSON hold under bash 3.20a6d71d0d
  • site a path in a claim or an issue title wraps inside a 320px card27db8a983
    I0830 docs/PERFORMANCE.md, README, CONTRIBUTING and CLI reference
  • scope migrate seeds the scope, knowledge reads it, case 65 ignores the budget linef28a5dad3
  • serve ask descriptor 0 whether stdin is a pipe, not the path /dev/stdin2356c588a
  • shell the plan model reads its rows under bash 3.26d3f18d39
  • site a path in a claim or an issue title wraps inside a 320px cardaae7115e1
    I0830 docs/PERFORMANCE.md, README, CONTRIBUTING and CLI reference
  • bench a baseline fails a run only on the host that recorded itcd3f04a43
  • serve ask descriptor 0 whether stdin is a pipe, not the path /dev/stdin8de168618
  • site plan and issue rows shrink at 320px instead of widening the page2a4537e9c
  • site a path in a claim or an issue title wraps inside a 320px cardff4406b50
    I0830 docs/PERFORMANCE.md, README, CONTRIBUTING and CLI reference
  • mcp settle_alone answers a Reply, as the session does since the prepared listings277b366cb
  • merge the YAML subset types decimals, and two cases stop counting objects.get's casesc7b937cf6
  • mcp nothing a client leaves behind locks the others out of the shared server4a2f20aac
  • mcp order resources with sort_by_key, as clippy 1.98 asksd3ed96886
  • context drop the document chain under budget before any record body2db43cc0a
  • doctrine separate registry rows with the one byte no rule value can carry4f8b55dff
  • state reading commands answer on a checkout with no local store yet6808848fc
  • migrate back up and remove the legacy provider body instead of carrying it into .ai9b9f14c33
  • paths derive the distribution root from the entry point, never the environmente6df13ad7
  • site-data the plan model reaches jq through files, not argv780a76b07
    M003 A session is a durable envelope, and knowledge is compiled from what is already canonical
  • site declare the inputs the generator reads, and use one fixture helper75e118cf2
  • claims a claim that belongs to no responsibility must say so45ff51821
  • checkpoint a finished task has no checkpoint due, so stop reporting one4c4b19a54
  • test assert the key a policy error names, not how it punctuates ite23c7e117
  • test assert the key a policy error names, not how it punctuates itfd48689df
  • site the overflow probe names what actually overflows7fa8057d6
  • ci the deploy waits for the measurement, not for a heuristic that predicts it0fdb682bb
  • prompts the shipped assets open with a heading, so they are valid Markdown6c680977a
  • policy a required key that is missing is reported, not turned into a shell errorc1c2686f5
  • site a claim's note may wrap, so a path in it cannot set the page widtha9c9cc000
  • site a sample says it is a sample2787b3b47
  • site the route map mirrors Zola's slug, and a canonical path may wrap1a50a2ccf
    I0001 Audit what actually plans work in this repository M000 Milestone and DAG driven development
  • site let a step's note wrap to its own line on a phonefb0eb1d56
  • site expand the generator's input globs in byte orderdf6b79b7b
  • ci export the subshell setting shellcheck cannot see through, regenerate9483779a1
  • derive what the tool knows about itself, and refuse a second copy920fce43a
  • docs PLAN_STATUS.md recorded the commit it was generated at, so it was stale on commit80ab7b25f
  • site refuse an invalid project model from the model's own findings5d63204fc
    M000 Milestone and DAG driven development
  • test the site fixtures copy the project registry the generator now requires95862bc25
  • site regenerate the manifest after editing one of its inputs8d4df52cf
  • site untrack two generated doctrine pages the new rule caughtdbf5b1107
  • site the doctrine filter announces its state, not only its colour70b5768e0
  • site derive the responsibility count instead of writing it38327c0e7
  • site parenthesise the edges pipeline so jq 1.7 parses it60f83e37c
  • test replace ls|grep with a glob loop in the why-route countf6488ca07
  • question the file's own template is not an entry, and publish the blocker gap204f1c792
  • state a task record names its checkout, and does not export its scope8efa84799
  • site derive the route check from generated content; match node_modules as a symlinkd0028b9ae
  • site point the npm scripts and gitignore at the current site scripts6b5aaafb7
  • start,check accumulate repeated --scope, tolerate spaces, normalise scope at read timea98a0a342
  • site min-w-0 on grid columns holding code; multi-line wrapper check in test 09940fdf45d
  • site carry the GitHub Pages path prefix on every generated path06e85990f
  • site make --no-css genuinely need no Nodeb24691ce9
  • site set core.hooksPath in pages, and stop citing generated files as sources2738c69f6
# Performance perf 23
# Changed refactor 13
# Documentation docs 82
  • deploy a preview publication is visible, and says so on the pagee40cefe9f
  • ci the reference gate in the model, and out of the suite's way2eb2c01bb
  • consolidation the forensic findings and the plan they justify95d9a773c
  • references every path a document names is a path that is theredf7dcc385
  • the directories say what lives in them, and every schema reference resolves17d3e1b23
  • why the schema paths and the assertion name the identity, not the old file029f26260
  • adr the capability graph is composed, not centralised, and projected twice665f1c4e8
  • session the working context declares itself where every other record does24af4a5de
  • use-cases the directory hierarchy is a question a client can askc81090d13
  • context a carried subtree is released by name, and the tool knows no names0704b1faf
  • why the schema paths the merge moved, and the assertion that quoted onec50befe3f
  • adr the episode decision takes 0017, and every projection followsef57411b4
  • claims the command line's documentation is a guarantee, not an accidentfb7a30f95
  • use-cases the directory hierarchy is a question a client can askfb30b23cf
  • context a carried subtree is released by name, and the tool knows no names1e0d176e7
  • use-cases the directory hierarchy is a question a client can ask9fa28449a
  • context a carried subtree is released by name, and the tool knows no namese8cd3339b
  • rules the case for a floor, from the branch that hit it70a299939
  • web the surface a reader can navigate, and the one a developer extendsfa0d8245d
  • web the Swagger UI is at /swagger, and a quoted URL is not a linkbc77bf6b0
  • claims what the two web-surface guarantees mean, and how to see them4e25cfc18
  • cockpit the Cockpit on the matrix it belongs to, and what it will not doc43f8bc9a
  • adr web surfaces are discovered from their producer and projected once8cee64583
  • cockpit the decision, the reference, and a use case that names it27f55987d
  • pages the publication path, its budgets and its evidence2e2299401
  • ai a native command exists only with its documentation and its executable examples8375d9ddf
  • use-cases the doctrine, the workflow, ADR 5 and the concepte358be230
  • ci the pages job publishes through scripts/site-deploy; the wiring case accepts ita7db43652
  • scope the doctrine, the claim, case 93 and the documentation104533222
  • one contributor workflow (just derive, just derive-check); the benchmark-policy edge tested; long path links wrap at 320px0aa1ce285
  • scope the doctrine, the claim, case 93 and the documentation8aa2e0051
  • architecture the documentation projection graph — stages, boundary, ownership, classification — with its claims and gates97e3986f1
  • adr ADR 5, one projection plan over named canonical owners, the site as a view of the registry312be2a1f
  • claims name the test file of mcp-uri-resolution as committed47e6aa520
  • openapi claim openapi-inferred, case 92, and the projection rows2f39b57a7
  • adr ADR 5, one projection plan over named canonical owners, the site as a view of the registrycdbe95c70
  • openapi claim openapi-inferred, case 92, and the projection rowsecdce9d01
  • scope the doctrine, the claim, case 93 and the documentation0240a2652
  • claims name the test file of mcp-uri-resolution as committed99f2137ee
  • adr ADR 5, one projection plan over named canonical owners, the site as a view of the registry3fad40b7f
  • ai codify the shared server's resilience as doctrineb806960a2
  • capability resolve the intra-doc links to the module macros2bba3cf88
  • mcp the shared server, peers and client auto-start, with their claims195b19416
  • capabilities the capability model as doctrine, with its claims, ADR, CI gates and the every-interface case56a5f4063
  • rust document every public item, add executable examples, raise coverage to 91%b070d3796
  • cli document the Rust executable and its MCP surface, and wire it into the checks7e2f5484f
  • ai codify simplicity and extensibility doctrine7e826bf4c
  • claims file the layer and migration claims under the layer responsibility46bfff17b
  • ai say exactly what init writes and what the bootstrap check detectsab450a1ce
  • ai rewrite README, CLI, CONCEPTS and DESIGN for the layer as it is82128fcf9
  • claims state the .ai layer's guarantees and bring the matrix to master semantics20a804d4c
  • ai document the manifest, the vendored package and the knowledge sources; sweep the last legacy paths4ec84dfdd
  • rules list exits 2 and 13, and say doctor does not read rule objects yet0d3e125f6
  • ai sweep the pre-.ai paths out of docs, claims and the sitee637f763c
  • readme the profiles row no longer says how many there aree7766ad40
  • continuity a session is the seventh record, and it is an envelope9c13909ca
    I0802 Specify the session record before writing one
  • design the boundary excludes semantic machinery, not a table of stated references3c9ba2f1c
    I0801 Narrow the Clean Extraction Boundary and record what was adopted
  • ledger record why no rule guards a declared readerfb43dfa07
  • architecture the de-hardcoding ledger and the ownership rules behind it503edce06
  • schemas decisions.md names the commands that read it4f9f55aee
  • plan evidence states what a command showed, not a count that goes stale2dc3f514a
    M000 Milestone and DAG driven development
  • claims the roadmap version comes from the milestone, not from prosee0d0e054c
  • claims task-dependencies says what is refused, not that no graph existscfd0f594e
  • correct why the input order diverged, and record the environment lessond48f9a636
    M000 Milestone and DAG driven development M001 A blocking question survives a handover
  • plan the planning semantics, the dogfooding rule, and the schemas behind them879efbd30
  • say that doctrines exist, where people actually readd7c9fa174
  • memory the continuity model, its schemas, and twelve claims with evidence2c4bbb4c2
  • complete the documentation index and correct claims that outran the codefb1be3eab
  • region projections, dispatcher wiring, and a flag that never existed87bbd51ae
  • economics cost decomposition, ledger-measurable metrics, per-outcome unit0107a0bad
  • record the base-path lesson as the cleaner two-writers example967a95b55
  • site document the deployment prefix and the Node-free generation moded24538f7c
  • site document the derived Pages architecture and content ownership5521c5da5
  • add logo, social card, and website link to README6a224ad8b
  • record the two-writers-one-checkout limitation observed while building v0.167c99d730
  • cross-reference CLI and schema specs from design and report0c7abaebf
  • expand README and add CLI, schema, contributing, and security docs6136dc3c5
  • point README at design, extraction report, and contract54a869e29
  • add extraction report, repo operating contract, and docs index9ce093642
  • design add typed outcomes, check --explain, presentation layerf0b4bc6ad
  • add v0.1 design specification232b2797b
  • add design-phase README556e524c2
# Tests test 52
  • lib a fixture carries what the templates read, not what one generator names3a0b38c13
  • lib a command can be quiet when it works and speak when it does not22c18f959
  • registry the removal case takes a capability the catalogue does not need77e2a7a17
  • ci three cases read the repository as it is33b52ebf6
  • rules the DAG case and the CLI reference read the enforcement column as it is printedae48c7051
  • ui the two cases this branch invalidated, both read from the model now1ccc432bf
  • generate the document schemas are projected where they belong, and proved so78cd4fae5
  • ci a gate that refuses a document naming a file that is not there368cd4ce9
  • ci a workflow is legitimate when it has a model, not when there are two of themc79ab0cef
  • cli every refusal of the documentation contract, provokedab94b74bb
  • generate a projected JSON Schema is JSON by its own contract6206079f4
  • ci a workflow is legitimate when it has a model, not when there are two of them0f67cd5fb
  • continuity the populated page, and a determinism check that stopped watching the clock537c54000
  • continuity the populated page, and a determinism check that stopped watching the clocke328d2f79
  • web the vocabulary, the selection and the renderings the gate had not seenb312f32ec
  • web the reserved names and the derived page, proven over a sockete3d8895b7
  • cockpit every route the server serves, and the interactions, in a real browser2614422a0
  • use-case prove the refusal of an undocumented directory by running iteb4ecf267
  • pages the fast path is held to the shape that makes it fast8a8925a67
  • suite the timing cases and the API page case run alone; two cases clear MAJORDOMUS_BIN2ca48d4bf
  • scope case 93 reads the diagnostics where mcp --inspect nests themb6468d87e
  • scope case 93 reads the diagnostics where mcp --inspect nests them7d8cd469b
  • projections the plan test writes nothing outside the fixture root6ca6a2cd7
  • site a capability that joins or leaves the registry manifest gains or loses its route; a broken manifest is refused6791e9e16
  • suite a bounded parallel runner, exclusive cases, and MAJORDOMUS_BIN for the Rust casese5de81170
  • cases a mutation case copies the site tree whole and reads the input list from --inputs2a73067c1
  • http replay every route's cases over a socket and time every routebbab30282
  • projections the plan test writes nothing outside the fixture root11a0acd67
  • http replay every route's cases over a socket and time every route82406d309
  • scope case 93 reads the diagnostics where mcp --inspect nests them8ec5922a9
  • bench the objects.get run has one result per declared case, not one14d958ebb
  • rust prove the Rust gates are wired, as three claims and case 77015e55aeb
  • cli the no-share check runs inside an initialised repositorye78732848
  • site fixtures carry every path the claims matrix namesff7d1a7fc
  • capabilities registry invariants, cross-projection identity, HTTP black box, cross-protocol parity, generate --check1e7761cb1
  • cli black-box coverage for the CLI, discovery, metadata, index, stdio MCP and extensibility68fde4bee
  • constructs allow the context-document scratch files in the write allow-list9a7adc757
  • context black-box cases for context impact and check-sync, against the contract62ce65ced
  • rules prove the rule DAG by mutation, dispatch `rules`, document rule objectsc58893378
  • site mutate the state reference the scanner now resolves20e0bac56
  • plan capture output instead of piping it into grep -qa08ecde76
  • plan capture output instead of piping it into grep -q646308dea
  • an empty derivation is a fault in the derivation, not an answerb559ce3b5
  • plan the roadmap graph gets its own mutation propagation proof955031ad9
  • site the committed derived artifacts are checked against this repository05423af46
  • plan cross-surface consistency and mutation propagation; CI gates the modelc4c12ac21
  • cli derive the command surface from the dispatch table359b45e2d
  • renumber the continuity cases to 20-26c31159b9d
  • memory behavioural, negative and integration cases, wired into CI3b22af408
  • lint the derived site for mobile-first and responsive constructs870c45ecd
  • portable file-mode check; gate the derived site in validate57e85e1fb
  • scan the tool's own source for forbidden constructsf3daaca36
# Pipeline ci 14
  • plan the cockpit probe is gated on an output the plan job declares40cf65522
  • pages the workflow's paths block follows the model again817ea7ba2
  • site one documentation source, two base pathsda48cba98
  • cockpit the stylesheet is a generated artifact, so a gate proves it currentf710d3472
  • suite the jobs that run the suite check out the whole historyc991d86cb
  • master runs are independent of one another; only deployments queue1e6edeafc
  • structure actionlint from a pinned release, not from install-action94926fa72
  • the workflow parses, and actionlint is part of the lint gate50056aa3f
  • one workflow over the plan; the site deploys from the run that verified itf0623b631
  • pages the site does not deploy from a stale registry dataset or bootstrapfea04fad7
  • pages the site does not deploy from a stale registry dataset or bootstrapb935ae090
  • pages the site does not deploy from a stale registry dataset or bootstrape80ded65f
  • site the complete probe runs in validate, and master's shellcheck is greena27dd1cfa
  • install site build dependencies in validate so the derived-site tests rune64e7af34
# Build build 1
  • derive one entry point for every derived artifact, one read-only gate, and the commit out of the derived data58e2cd45b
# Pipeline ci 14
  • plan the cockpit probe is gated on an output the plan job declares40cf65522
  • pages the workflow's paths block follows the model again817ea7ba2
  • site one documentation source, two base pathsda48cba98
  • cockpit the stylesheet is a generated artifact, so a gate proves it currentf710d3472
  • suite the jobs that run the suite check out the whole historyc991d86cb
  • master runs are independent of one another; only deployments queue1e6edeafc
  • structure actionlint from a pinned release, not from install-action94926fa72
  • the workflow parses, and actionlint is part of the lint gate50056aa3f
  • one workflow over the plan; the site deploys from the run that verified itf0623b631
  • pages the site does not deploy from a stale registry dataset or bootstrapfea04fad7
  • pages the site does not deploy from a stale registry dataset or bootstrapb935ae090
  • pages the site does not deploy from a stale registry dataset or bootstrape80ded65f
  • site the complete probe runs in validate, and master's shellcheck is greena27dd1cfa
  • install site build dependencies in validate so the derived-site tests rune64e7af34
# Housekeeping chore 153
  • release 0.3.1, the version the fixed pipeline releases032cc0025
  • derive the projections follow the merges1fd5e32e0
  • derive the projections follow the merge with master748de838d
  • derive the claim is an object of the index once it is tracked3d649ae3b
  • derive the projections follow the gate and the versionfb5bbeb01
  • derive the projections follow the merges51a39cacc
  • derive the projections follow the fold89aec9654
  • derive the projections follow the mergesf9a1a4482
  • derive the projections follow the merged treeeac7c97ba
  • derive the projections follow the merge of masterdb64b42bf
  • derive the projections follow the merge of mastera568ee4c4
  • derive the projections follow the rebase onto masterdfcc21f19
  • sessions record two feature/ai-artifacts episodesbfffc0b1f
  • derive the projections follow the merge with master4bca63379
  • derive every projection regenerated over the integrated treec83f763fb
  • derive the projections follow the merged tree347c94342
  • sessions record two feature/ai-artifacts episodesc027ef6ea
  • plan I1003 done, with the evidence the contract asked for701d3780c
    I1003 Skills, rules, decisions, documents, use cases and benchmarks enter the graph as themselves
  • plan I1025 done, with the evidence the contract asked fora1fc8d8ac
    I1025 The federated model and its two projections are an architecture decision
  • plan I1004 done, with the evidence the contract asked for5b817c2eb
    I1004 Availability and visibility are metadata, not conditions in a template
  • plan I1002 done, with the evidence the contract asked for46da8089d
    I1002 Relations are typed, inferred from stable identities, and never dangle
  • derive the plan projection follows the two new milestones72544e632
  • derive the projections follow the capture fixes3fa38210f
  • plan I1001 done, with the evidence the contract asked fora4979a09b
    I1001 One typed graph composes the registries that already own their facts
  • derive the projections follow the merge with master988e928ee
  • derive every projection regenerated over the merge5961be109
  • derive every projection regenerated over the mergebb93f91d8
  • derive the site registry settlesedba7a9c5
  • derive the projections follow the rebase onto master730f4b167
  • derive every projection regenerated over the merge5ba3d60b6
  • derive the site registry follows the tree1f7955968
  • derive the mirrored status page settles on the second pass67a17cea1
  • derive the site follows the ported schema and the use case33fca6129
  • derive regenerate the projections after the rebase305b7f743
  • derive the registry dataset over the capture fix5d0e628ef
  • derive the registry dataset over the objects the last commits addedb3d05ae1d
  • derive the pages status over the inputs as they finally area2bb43fca
  • derive the site dataset and the formatting the rebase left behind4137b87bc
  • derive the registry over the tree master merged into0a13b50e3
  • derive the site dataset follows the rebased treec79b16c6e
  • derive the registry regenerated over the rebased tree32572bc9f
  • sessions the episodes that built this, closed by the events they addedacb0c173a
  • derive regenerate after rebasing the claim onto master0b0c104ba
  • derive the site registry follows the treec7f35c23c
  • derive the mirrored status page settles on the second passae4072bbc
  • derive the site follows the ported schema and the use case12668bb7b
  • derive regenerate the projections after the rebase42319a792
  • derive regenerate over the mergeb46d727e7
  • derive the registry dataset over the objects the last commits added2af35cbc3
  • derive the pages status over the inputs as they finally areced26b02c
  • derive regenerate over the merge, migrate one use case, renumber the ADR to 0016df138c2e5
  • derive the projections follow the strict gate onto the merged tree0169c885e
  • derive regenerate the projections after the rebasea70fdbc34
  • derive the site dataset and the formatting the rebase left behinde08bfcc77
  • derive regenerate over the merged session work6a584e688
  • derive the projections follow the tree, so the site can publish againd4e0ed7fb
  • derive regenerate after the merges, so the publication path accepts the tree0d9c347b3
  • derive the registry over the tree master merged into86ce0e7d8
  • derive the site dataset follows the rebased tree44d2806a6
  • derive the registry regenerated over the rebased tree6a585031e
  • sessions the episodes that built this, closed by the events they added921ab6b16
  • derive regenerate over the merge129bfe1a8
  • derive settle the mirrored status page7da59b1c1
  • derive regenerate over the merged treee17a73ead
  • derive regenerate over the merged treed847b3226
  • derive regenerate every derived artifact after the session lifecycle landedc852dea59
  • derive every projection regenerated from the merged tree62b71b3b6
  • site the plan projection follows the two new milestones73e76c1f1
  • derive the second pass the index needs after the first4658856fe
  • derive regenerate every projection over the merged tree235c47106
  • derive the projections follow the web command and its reports56372e100
  • web the generated web root is ignored, like every other derived tree9bb67d64c
  • site the website follows the registry and the docs index, regeneratedef755d41c
  • cockpit vendor the module build the page actually loads, and the dataset0d26ed9c5
  • derive the site dataset follows the two assertions that movedeaad9f682
  • derive one registry for one tree, at the tip9e224d050
  • derive regenerate the projections this branch owns, from a clean tree53b1d1c6c
  • derive the pages-status stamp, current with the inputs it was computed overde48006e3
  • derive regenerate over the decision subsystem and its two use casesbc32cac72
  • derive the pages-status page, current with the document it projectseba8bdbda
  • derive regenerate for the generator and performance-doc changedefed0c27
  • derive regenerate after integrating the prompt capturea0ccbc9e2
  • derive regenerate the derived artifacts over the integrated tree8cab3ebcf
  • derive regenerate the derived artifacts after merging the Pages fast path8e14274b6
  • derive regenerate the registry dataset over the tracked tree02b2e3e9f
  • derive regenerate for the third skill and the skills use caseef2136dc3
  • derive regenerate the site data and the registry dataset for the two skills9525f6280
  • site regenerate the derived data for the hero branch2cdc96310
  • derive regenerate on the merged treefa9db2be4
  • derive regenerate the registry dataset after the usecase library changec06271f54
  • derive regenerate on the merged treee90b347f0
  • derive regenerate every projection and the site data on the merged tree629ebf8a3
  • derive regenerate after merging PR #38 onto the scope policy31acaf90d
  • derive regenerate the projections, the OpenAPI document and the site data after the mergese31aceb75
  • derive regenerate the registry dataset and the site data after rebasing onto 4bbd72655452d619
  • derive regenerate the site data and the registry dataset after merging PR #304bbd7266d
  • bench re-record the macos-aarch64-debug baseline with its host (Apple M5 Pro/18)5f538d4c7
  • derive regenerate the derived data after merging origin/master32f796175
  • derive regenerate the site data and the registry dataset after rebasing onto 0481024b1be56192
  • site-data regenerate after the case 65 change1282a3630
  • derive regenerate the site data and the registry dataset after rebasing onto 77e28a804221ad38
  • derive regenerate the site data and the registry dataset after rebasing onto b9f1091080adee37
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc625b845f33a
  • site regenerate the registry dataset after its own claim joined the index24bb212a2
  • site-data regenerate after the test-case change0bf5f316d
  • derive regenerate the derived data after integrating PR #30, #31, #32 and #335b0e3e807
  • derive regenerate the site data and the registry dataset after rebasing onto b9f10914656b0be5
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc6281921eec1
  • site regenerate the registry dataset after its own claim joined the index5afb9bf57
  • bench re-record the macos-aarch64-debug baseline with its host (Apple M5 Pro/18)ff078af73
  • site-data regenerate for the case 28 probe changeb9f109147
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc62614b7b13a
  • site regenerate the registry dataset after its own claim joined the index1b017bad4
  • site-data regenerate the derived data after merging feature/mcp-shared-servercb9dc62b1
  • bench record the macos-aarch64-debug baseline from a clean tree at 1acda1d65ccf7835
  • projections restamp AGENTS.md and CLAUDE.md for the merged policy38093b339
  • generated regenerate the reference, the registry manifest and the site data after the merges08a235cf6
  • site-data regenerate after rebasing onto the merged Rust CLIda14b6414
  • site-data regenerate the plan status after the rebase onto master9d6339b14
  • site-data regenerate after the context claims and rule joined the inputs5e10fda21
  • rules a maintainer entry point for the shipped package manifestcbce33c79
  • site-data regenerate after the layer responsibility change6aba73108
  • rules wire the layer's claims into the rules that back theme2406d9cb
  • state close the plan-page task and start the .ai transformation task6d3b73b2e
  • state checkpoint that v0.1.0 is taggede85269422
  • site-data regenerate source.json at the checkpoint commitaabee071b
  • state checkpoint the responsibilities and argv work31f8b7bdc
  • state record why the enforcement gap was taken outside the plan29a5879ef
  • gitignore ignore local scratch directoriesca66fca22
  • state close the stale-base task and reopen at the current commit7ba86aeb8
  • site-data regenerate after RESPONSIBILITIES.yaml joined the inputsd6aca744e
  • state session records for the derived-plan-page task31965b1dc
  • site regenerate derived data after merging master07a71d563
  • site regenerate derived data after merging mastere792ebe8a
  • site regenerate after merging the doctrine brancha726e3cfc
  • site regenerate derived data after merging master94d2180ad
  • site regenerate after the merge5ea2fa7ec
  • site regenerate the derived data after merging master8c26a8e72
  • plan the suite evidence cites the run that covers every case40b6f3bfd
    I0010 Behavioural tests for schema, status, graph and command M000 Milestone and DAG driven development
  • site regenerate after the self-derivation and shellcheck fixes252a0dab2
  • site regenerate the derived data after merging the plan work99053b8c1
  • site regenerate derived data after the rebase7e88948fe
  • state checkpoint at the end of M0006563fc4a3
    M000 Milestone and DAG driven development
  • state the merge brought .gitignore into this task's diff rangeee0a12849
  • state close the stale-base task and start again at the current commit615c2b298
  • state widen the task scope to the projection targets and the README2dd5915d6
  • site regenerate after rebasee818a9d5e
  • site regenerate after rebase; new claims landed upstreama785baef2
  • state the audit task was scoped for writing, not for finding1555bf5b7
  • state close the worktree-ownership task; its base predates a peer's commits1e2bcfe50
  • state close the active task; it was gating other worktreesd95773ad7
  • state record the scope violation and the task that follows itbeb7b074c
  • site regenerate derived site data after the rebase477239041
# Formatting style 6
  • rust the crate is formatted as rustfmt wants it, and the projections follow7515a2b49
  • rust the crate is formatted, so the rust gate can fail for a reason5ae59e5fc
  • rust cargo fmt over the integrated tree, and the scope fixture's own limit1dbacfeb2
  • rust the crate is formatted as rustfmt wants itfead190a1
  • rust cargo fmt over the merged tree088ba7c86
  • tests one line rustfmt rewraps, so the rust gate can reach the rest6a2509c21
# Housekeeping chore 153
  • release 0.3.1, the version the fixed pipeline releases032cc0025
  • derive the projections follow the merges1fd5e32e0
  • derive the projections follow the merge with master748de838d
  • derive the claim is an object of the index once it is tracked3d649ae3b
  • derive the projections follow the gate and the versionfb5bbeb01
  • derive the projections follow the merges51a39cacc
  • derive the projections follow the fold89aec9654
  • derive the projections follow the mergesf9a1a4482
  • derive the projections follow the merged treeeac7c97ba
  • derive the projections follow the merge of masterdb64b42bf
  • derive the projections follow the merge of mastera568ee4c4
  • derive the projections follow the rebase onto masterdfcc21f19
  • sessions record two feature/ai-artifacts episodesbfffc0b1f
  • derive the projections follow the merge with master4bca63379
  • derive every projection regenerated over the integrated treec83f763fb
  • derive the projections follow the merged tree347c94342
  • sessions record two feature/ai-artifacts episodesc027ef6ea
  • plan I1003 done, with the evidence the contract asked for701d3780c
    I1003 Skills, rules, decisions, documents, use cases and benchmarks enter the graph as themselves
  • plan I1025 done, with the evidence the contract asked fora1fc8d8ac
    I1025 The federated model and its two projections are an architecture decision
  • plan I1004 done, with the evidence the contract asked for5b817c2eb
    I1004 Availability and visibility are metadata, not conditions in a template
  • plan I1002 done, with the evidence the contract asked for46da8089d
    I1002 Relations are typed, inferred from stable identities, and never dangle
  • derive the plan projection follows the two new milestones72544e632
  • derive the projections follow the capture fixes3fa38210f
  • plan I1001 done, with the evidence the contract asked fora4979a09b
    I1001 One typed graph composes the registries that already own their facts
  • derive the projections follow the merge with master988e928ee
  • derive every projection regenerated over the merge5961be109
  • derive every projection regenerated over the mergebb93f91d8
  • derive the site registry settlesedba7a9c5
  • derive the projections follow the rebase onto master730f4b167
  • derive every projection regenerated over the merge5ba3d60b6
  • derive the site registry follows the tree1f7955968
  • derive the mirrored status page settles on the second pass67a17cea1
  • derive the site follows the ported schema and the use case33fca6129
  • derive regenerate the projections after the rebase305b7f743
  • derive the registry dataset over the capture fix5d0e628ef
  • derive the registry dataset over the objects the last commits addedb3d05ae1d
  • derive the pages status over the inputs as they finally area2bb43fca
  • derive the site dataset and the formatting the rebase left behind4137b87bc
  • derive the registry over the tree master merged into0a13b50e3
  • derive the site dataset follows the rebased treec79b16c6e
  • derive the registry regenerated over the rebased tree32572bc9f
  • sessions the episodes that built this, closed by the events they addedacb0c173a
  • derive regenerate after rebasing the claim onto master0b0c104ba
  • derive the site registry follows the treec7f35c23c
  • derive the mirrored status page settles on the second passae4072bbc
  • derive the site follows the ported schema and the use case12668bb7b
  • derive regenerate the projections after the rebase42319a792
  • derive regenerate over the mergeb46d727e7
  • derive the registry dataset over the objects the last commits added2af35cbc3
  • derive the pages status over the inputs as they finally areced26b02c
  • derive regenerate over the merge, migrate one use case, renumber the ADR to 0016df138c2e5
  • derive the projections follow the strict gate onto the merged tree0169c885e
  • derive regenerate the projections after the rebasea70fdbc34
  • derive the site dataset and the formatting the rebase left behinde08bfcc77
  • derive regenerate over the merged session work6a584e688
  • derive the projections follow the tree, so the site can publish againd4e0ed7fb
  • derive regenerate after the merges, so the publication path accepts the tree0d9c347b3
  • derive the registry over the tree master merged into86ce0e7d8
  • derive the site dataset follows the rebased tree44d2806a6
  • derive the registry regenerated over the rebased tree6a585031e
  • sessions the episodes that built this, closed by the events they added921ab6b16
  • derive regenerate over the merge129bfe1a8
  • derive settle the mirrored status page7da59b1c1
  • derive regenerate over the merged treee17a73ead
  • derive regenerate over the merged treed847b3226
  • derive regenerate every derived artifact after the session lifecycle landedc852dea59
  • derive every projection regenerated from the merged tree62b71b3b6
  • site the plan projection follows the two new milestones73e76c1f1
  • derive the second pass the index needs after the first4658856fe
  • derive regenerate every projection over the merged tree235c47106
  • derive the projections follow the web command and its reports56372e100
  • web the generated web root is ignored, like every other derived tree9bb67d64c
  • site the website follows the registry and the docs index, regeneratedef755d41c
  • cockpit vendor the module build the page actually loads, and the dataset0d26ed9c5
  • derive the site dataset follows the two assertions that movedeaad9f682
  • derive one registry for one tree, at the tip9e224d050
  • derive regenerate the projections this branch owns, from a clean tree53b1d1c6c
  • derive the pages-status stamp, current with the inputs it was computed overde48006e3
  • derive regenerate over the decision subsystem and its two use casesbc32cac72
  • derive the pages-status page, current with the document it projectseba8bdbda
  • derive regenerate for the generator and performance-doc changedefed0c27
  • derive regenerate after integrating the prompt capturea0ccbc9e2
  • derive regenerate the derived artifacts over the integrated tree8cab3ebcf
  • derive regenerate the derived artifacts after merging the Pages fast path8e14274b6
  • derive regenerate the registry dataset over the tracked tree02b2e3e9f
  • derive regenerate for the third skill and the skills use caseef2136dc3
  • derive regenerate the site data and the registry dataset for the two skills9525f6280
  • site regenerate the derived data for the hero branch2cdc96310
  • derive regenerate on the merged treefa9db2be4
  • derive regenerate the registry dataset after the usecase library changec06271f54
  • derive regenerate on the merged treee90b347f0
  • derive regenerate every projection and the site data on the merged tree629ebf8a3
  • derive regenerate after merging PR #38 onto the scope policy31acaf90d
  • derive regenerate the projections, the OpenAPI document and the site data after the mergese31aceb75
  • derive regenerate the registry dataset and the site data after rebasing onto 4bbd72655452d619
  • derive regenerate the site data and the registry dataset after merging PR #304bbd7266d
  • bench re-record the macos-aarch64-debug baseline with its host (Apple M5 Pro/18)5f538d4c7
  • derive regenerate the derived data after merging origin/master32f796175
  • derive regenerate the site data and the registry dataset after rebasing onto 0481024b1be56192
  • site-data regenerate after the case 65 change1282a3630
  • derive regenerate the site data and the registry dataset after rebasing onto 77e28a804221ad38
  • derive regenerate the site data and the registry dataset after rebasing onto b9f1091080adee37
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc625b845f33a
  • site regenerate the registry dataset after its own claim joined the index24bb212a2
  • site-data regenerate after the test-case change0bf5f316d
  • derive regenerate the derived data after integrating PR #30, #31, #32 and #335b0e3e807
  • derive regenerate the site data and the registry dataset after rebasing onto b9f10914656b0be5
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc6281921eec1
  • site regenerate the registry dataset after its own claim joined the index5afb9bf57
  • bench re-record the macos-aarch64-debug baseline with its host (Apple M5 Pro/18)ff078af73
  • site-data regenerate for the case 28 probe changeb9f109147
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc62614b7b13a
  • site regenerate the registry dataset after its own claim joined the index1b017bad4
  • site-data regenerate the derived data after merging feature/mcp-shared-servercb9dc62b1
  • bench record the macos-aarch64-debug baseline from a clean tree at 1acda1d65ccf7835
  • projections restamp AGENTS.md and CLAUDE.md for the merged policy38093b339
  • generated regenerate the reference, the registry manifest and the site data after the merges08a235cf6
  • site-data regenerate after rebasing onto the merged Rust CLIda14b6414
  • site-data regenerate the plan status after the rebase onto master9d6339b14
  • site-data regenerate after the context claims and rule joined the inputs5e10fda21
  • rules a maintainer entry point for the shipped package manifestcbce33c79
  • site-data regenerate after the layer responsibility change6aba73108
  • rules wire the layer's claims into the rules that back theme2406d9cb
  • state close the plan-page task and start the .ai transformation task6d3b73b2e
  • state checkpoint that v0.1.0 is taggede85269422
  • site-data regenerate source.json at the checkpoint commitaabee071b
  • state checkpoint the responsibilities and argv work31f8b7bdc
  • state record why the enforcement gap was taken outside the plan29a5879ef
  • gitignore ignore local scratch directoriesca66fca22
  • state close the stale-base task and reopen at the current commit7ba86aeb8
  • site-data regenerate after RESPONSIBILITIES.yaml joined the inputsd6aca744e
  • state session records for the derived-plan-page task31965b1dc
  • site regenerate derived data after merging master07a71d563
  • site regenerate derived data after merging mastere792ebe8a
  • site regenerate after merging the doctrine brancha726e3cfc
  • site regenerate derived data after merging master94d2180ad
  • site regenerate after the merge5ea2fa7ec
  • site regenerate the derived data after merging master8c26a8e72
  • plan the suite evidence cites the run that covers every case40b6f3bfd
    I0010 Behavioural tests for schema, status, graph and command M000 Milestone and DAG driven development
  • site regenerate after the self-derivation and shellcheck fixes252a0dab2
  • site regenerate the derived data after merging the plan work99053b8c1
  • site regenerate derived data after the rebase7e88948fe
  • state checkpoint at the end of M0006563fc4a3
    M000 Milestone and DAG driven development
  • state the merge brought .gitignore into this task's diff rangeee0a12849
  • state close the stale-base task and start again at the current commit615c2b298
  • state widen the task scope to the projection targets and the README2dd5915d6
  • site regenerate after rebasee818a9d5e
  • site regenerate after rebase; new claims landed upstreama785baef2
  • state the audit task was scoped for writing, not for finding1555bf5b7
  • state close the worktree-ownership task; its base predates a peer's commits1e2bcfe50
  • state close the active task; it was gating other worktreesd95773ad7
  • state record the scope violation and the task that follows itbeb7b074c
  • site regenerate derived site data after the rebase477239041
# Formatting style 6
  • rust the crate is formatted as rustfmt wants it, and the projections follow7515a2b49
  • rust the crate is formatted, so the rust gate can fail for a reason5ae59e5fc
  • rust cargo fmt over the integrated tree, and the scope fixture's own limit1dbacfeb2
  • rust the crate is formatted as rustfmt wants itfead190a1
  • rust cargo fmt over the merged tree088ba7c86
  • tests one line rustfmt rewraps, so the rust gate can reach the rest6a2509c21
# Housekeeping chore 153
  • release 0.3.1, the version the fixed pipeline releases032cc0025
  • derive the projections follow the merges1fd5e32e0
  • derive the projections follow the merge with master748de838d
  • derive the claim is an object of the index once it is tracked3d649ae3b
  • derive the projections follow the gate and the versionfb5bbeb01
  • derive the projections follow the merges51a39cacc
  • derive the projections follow the fold89aec9654
  • derive the projections follow the mergesf9a1a4482
  • derive the projections follow the merged treeeac7c97ba
  • derive the projections follow the merge of masterdb64b42bf
  • derive the projections follow the merge of mastera568ee4c4
  • derive the projections follow the rebase onto masterdfcc21f19
  • sessions record two feature/ai-artifacts episodesbfffc0b1f
  • derive the projections follow the merge with master4bca63379
  • derive every projection regenerated over the integrated treec83f763fb
  • derive the projections follow the merged tree347c94342
  • sessions record two feature/ai-artifacts episodesc027ef6ea
  • plan I1003 done, with the evidence the contract asked for701d3780c
    I1003 Skills, rules, decisions, documents, use cases and benchmarks enter the graph as themselves
  • plan I1025 done, with the evidence the contract asked fora1fc8d8ac
    I1025 The federated model and its two projections are an architecture decision
  • plan I1004 done, with the evidence the contract asked for5b817c2eb
    I1004 Availability and visibility are metadata, not conditions in a template
  • plan I1002 done, with the evidence the contract asked for46da8089d
    I1002 Relations are typed, inferred from stable identities, and never dangle
  • derive the plan projection follows the two new milestones72544e632
  • derive the projections follow the capture fixes3fa38210f
  • plan I1001 done, with the evidence the contract asked fora4979a09b
    I1001 One typed graph composes the registries that already own their facts
  • derive the projections follow the merge with master988e928ee
  • derive every projection regenerated over the merge5961be109
  • derive every projection regenerated over the mergebb93f91d8
  • derive the site registry settlesedba7a9c5
  • derive the projections follow the rebase onto master730f4b167
  • derive every projection regenerated over the merge5ba3d60b6
  • derive the site registry follows the tree1f7955968
  • derive the mirrored status page settles on the second pass67a17cea1
  • derive the site follows the ported schema and the use case33fca6129
  • derive regenerate the projections after the rebase305b7f743
  • derive the registry dataset over the capture fix5d0e628ef
  • derive the registry dataset over the objects the last commits addedb3d05ae1d
  • derive the pages status over the inputs as they finally area2bb43fca
  • derive the site dataset and the formatting the rebase left behind4137b87bc
  • derive the registry over the tree master merged into0a13b50e3
  • derive the site dataset follows the rebased treec79b16c6e
  • derive the registry regenerated over the rebased tree32572bc9f
  • sessions the episodes that built this, closed by the events they addedacb0c173a
  • derive regenerate after rebasing the claim onto master0b0c104ba
  • derive the site registry follows the treec7f35c23c
  • derive the mirrored status page settles on the second passae4072bbc
  • derive the site follows the ported schema and the use case12668bb7b
  • derive regenerate the projections after the rebase42319a792
  • derive regenerate over the mergeb46d727e7
  • derive the registry dataset over the objects the last commits added2af35cbc3
  • derive the pages status over the inputs as they finally areced26b02c
  • derive regenerate over the merge, migrate one use case, renumber the ADR to 0016df138c2e5
  • derive the projections follow the strict gate onto the merged tree0169c885e
  • derive regenerate the projections after the rebasea70fdbc34
  • derive the site dataset and the formatting the rebase left behinde08bfcc77
  • derive regenerate over the merged session work6a584e688
  • derive the projections follow the tree, so the site can publish againd4e0ed7fb
  • derive regenerate after the merges, so the publication path accepts the tree0d9c347b3
  • derive the registry over the tree master merged into86ce0e7d8
  • derive the site dataset follows the rebased tree44d2806a6
  • derive the registry regenerated over the rebased tree6a585031e
  • sessions the episodes that built this, closed by the events they added921ab6b16
  • derive regenerate over the merge129bfe1a8
  • derive settle the mirrored status page7da59b1c1
  • derive regenerate over the merged treee17a73ead
  • derive regenerate over the merged treed847b3226
  • derive regenerate every derived artifact after the session lifecycle landedc852dea59
  • derive every projection regenerated from the merged tree62b71b3b6
  • site the plan projection follows the two new milestones73e76c1f1
  • derive the second pass the index needs after the first4658856fe
  • derive regenerate every projection over the merged tree235c47106
  • derive the projections follow the web command and its reports56372e100
  • web the generated web root is ignored, like every other derived tree9bb67d64c
  • site the website follows the registry and the docs index, regeneratedef755d41c
  • cockpit vendor the module build the page actually loads, and the dataset0d26ed9c5
  • derive the site dataset follows the two assertions that movedeaad9f682
  • derive one registry for one tree, at the tip9e224d050
  • derive regenerate the projections this branch owns, from a clean tree53b1d1c6c
  • derive the pages-status stamp, current with the inputs it was computed overde48006e3
  • derive regenerate over the decision subsystem and its two use casesbc32cac72
  • derive the pages-status page, current with the document it projectseba8bdbda
  • derive regenerate for the generator and performance-doc changedefed0c27
  • derive regenerate after integrating the prompt capturea0ccbc9e2
  • derive regenerate the derived artifacts over the integrated tree8cab3ebcf
  • derive regenerate the derived artifacts after merging the Pages fast path8e14274b6
  • derive regenerate the registry dataset over the tracked tree02b2e3e9f
  • derive regenerate for the third skill and the skills use caseef2136dc3
  • derive regenerate the site data and the registry dataset for the two skills9525f6280
  • site regenerate the derived data for the hero branch2cdc96310
  • derive regenerate on the merged treefa9db2be4
  • derive regenerate the registry dataset after the usecase library changec06271f54
  • derive regenerate on the merged treee90b347f0
  • derive regenerate every projection and the site data on the merged tree629ebf8a3
  • derive regenerate after merging PR #38 onto the scope policy31acaf90d
  • derive regenerate the projections, the OpenAPI document and the site data after the mergese31aceb75
  • derive regenerate the registry dataset and the site data after rebasing onto 4bbd72655452d619
  • derive regenerate the site data and the registry dataset after merging PR #304bbd7266d
  • bench re-record the macos-aarch64-debug baseline with its host (Apple M5 Pro/18)5f538d4c7
  • derive regenerate the derived data after merging origin/master32f796175
  • derive regenerate the site data and the registry dataset after rebasing onto 0481024b1be56192
  • site-data regenerate after the case 65 change1282a3630
  • derive regenerate the site data and the registry dataset after rebasing onto 77e28a804221ad38
  • derive regenerate the site data and the registry dataset after rebasing onto b9f1091080adee37
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc625b845f33a
  • site regenerate the registry dataset after its own claim joined the index24bb212a2
  • site-data regenerate after the test-case change0bf5f316d
  • derive regenerate the derived data after integrating PR #30, #31, #32 and #335b0e3e807
  • derive regenerate the site data and the registry dataset after rebasing onto b9f10914656b0be5
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc6281921eec1
  • site regenerate the registry dataset after its own claim joined the index5afb9bf57
  • bench re-record the macos-aarch64-debug baseline with its host (Apple M5 Pro/18)ff078af73
  • site-data regenerate for the case 28 probe changeb9f109147
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc62614b7b13a
  • site regenerate the registry dataset after its own claim joined the index1b017bad4
  • site-data regenerate the derived data after merging feature/mcp-shared-servercb9dc62b1
  • bench record the macos-aarch64-debug baseline from a clean tree at 1acda1d65ccf7835
  • projections restamp AGENTS.md and CLAUDE.md for the merged policy38093b339
  • generated regenerate the reference, the registry manifest and the site data after the merges08a235cf6
  • site-data regenerate after rebasing onto the merged Rust CLIda14b6414
  • site-data regenerate the plan status after the rebase onto master9d6339b14
  • site-data regenerate after the context claims and rule joined the inputs5e10fda21
  • rules a maintainer entry point for the shipped package manifestcbce33c79
  • site-data regenerate after the layer responsibility change6aba73108
  • rules wire the layer's claims into the rules that back theme2406d9cb
  • state close the plan-page task and start the .ai transformation task6d3b73b2e
  • state checkpoint that v0.1.0 is taggede85269422
  • site-data regenerate source.json at the checkpoint commitaabee071b
  • state checkpoint the responsibilities and argv work31f8b7bdc
  • state record why the enforcement gap was taken outside the plan29a5879ef
  • gitignore ignore local scratch directoriesca66fca22
  • state close the stale-base task and reopen at the current commit7ba86aeb8
  • site-data regenerate after RESPONSIBILITIES.yaml joined the inputsd6aca744e
  • state session records for the derived-plan-page task31965b1dc
  • site regenerate derived data after merging master07a71d563
  • site regenerate derived data after merging mastere792ebe8a
  • site regenerate after merging the doctrine brancha726e3cfc
  • site regenerate derived data after merging master94d2180ad
  • site regenerate after the merge5ea2fa7ec
  • site regenerate the derived data after merging master8c26a8e72
  • plan the suite evidence cites the run that covers every case40b6f3bfd
    I0010 Behavioural tests for schema, status, graph and command M000 Milestone and DAG driven development
  • site regenerate after the self-derivation and shellcheck fixes252a0dab2
  • site regenerate the derived data after merging the plan work99053b8c1
  • site regenerate derived data after the rebase7e88948fe
  • state checkpoint at the end of M0006563fc4a3
    M000 Milestone and DAG driven development
  • state the merge brought .gitignore into this task's diff rangeee0a12849
  • state close the stale-base task and start again at the current commit615c2b298
  • state widen the task scope to the projection targets and the README2dd5915d6
  • site regenerate after rebasee818a9d5e
  • site regenerate after rebase; new claims landed upstreama785baef2
  • state the audit task was scoped for writing, not for finding1555bf5b7
  • state close the worktree-ownership task; its base predates a peer's commits1e2bcfe50
  • state close the active task; it was gating other worktreesd95773ad7
  • state record the scope violation and the task that follows itbeb7b074c
  • site regenerate derived site data after the rebase477239041
# Formatting style 6
  • rust the crate is formatted as rustfmt wants it, and the projections follow7515a2b49
  • rust the crate is formatted, so the rust gate can fail for a reason5ae59e5fc
  • rust cargo fmt over the integrated tree, and the scope fixture's own limit1dbacfeb2
  • rust the crate is formatted as rustfmt wants itfead190a1
  • rust cargo fmt over the merged tree088ba7c86
  • tests one line rustfmt rewraps, so the rust gate can reach the rest6a2509c21
# Housekeeping chore 153
  • release 0.3.1, the version the fixed pipeline releases032cc0025
  • derive the projections follow the merges1fd5e32e0
  • derive the projections follow the merge with master748de838d
  • derive the claim is an object of the index once it is tracked3d649ae3b
  • derive the projections follow the gate and the versionfb5bbeb01
  • derive the projections follow the merges51a39cacc
  • derive the projections follow the fold89aec9654
  • derive the projections follow the mergesf9a1a4482
  • derive the projections follow the merged treeeac7c97ba
  • derive the projections follow the merge of masterdb64b42bf
  • derive the projections follow the merge of mastera568ee4c4
  • derive the projections follow the rebase onto masterdfcc21f19
  • sessions record two feature/ai-artifacts episodesbfffc0b1f
  • derive the projections follow the merge with master4bca63379
  • derive every projection regenerated over the integrated treec83f763fb
  • derive the projections follow the merged tree347c94342
  • sessions record two feature/ai-artifacts episodesc027ef6ea
  • plan I1003 done, with the evidence the contract asked for701d3780c
    I1003 Skills, rules, decisions, documents, use cases and benchmarks enter the graph as themselves
  • plan I1025 done, with the evidence the contract asked fora1fc8d8ac
    I1025 The federated model and its two projections are an architecture decision
  • plan I1004 done, with the evidence the contract asked for5b817c2eb
    I1004 Availability and visibility are metadata, not conditions in a template
  • plan I1002 done, with the evidence the contract asked for46da8089d
    I1002 Relations are typed, inferred from stable identities, and never dangle
  • derive the plan projection follows the two new milestones72544e632
  • derive the projections follow the capture fixes3fa38210f
  • plan I1001 done, with the evidence the contract asked fora4979a09b
    I1001 One typed graph composes the registries that already own their facts
  • derive the projections follow the merge with master988e928ee
  • derive every projection regenerated over the merge5961be109
  • derive every projection regenerated over the mergebb93f91d8
  • derive the site registry settlesedba7a9c5
  • derive the projections follow the rebase onto master730f4b167
  • derive every projection regenerated over the merge5ba3d60b6
  • derive the site registry follows the tree1f7955968
  • derive the mirrored status page settles on the second pass67a17cea1
  • derive the site follows the ported schema and the use case33fca6129
  • derive regenerate the projections after the rebase305b7f743
  • derive the registry dataset over the capture fix5d0e628ef
  • derive the registry dataset over the objects the last commits addedb3d05ae1d
  • derive the pages status over the inputs as they finally area2bb43fca
  • derive the site dataset and the formatting the rebase left behind4137b87bc
  • derive the registry over the tree master merged into0a13b50e3
  • derive the site dataset follows the rebased treec79b16c6e
  • derive the registry regenerated over the rebased tree32572bc9f
  • sessions the episodes that built this, closed by the events they addedacb0c173a
  • derive regenerate after rebasing the claim onto master0b0c104ba
  • derive the site registry follows the treec7f35c23c
  • derive the mirrored status page settles on the second passae4072bbc
  • derive the site follows the ported schema and the use case12668bb7b
  • derive regenerate the projections after the rebase42319a792
  • derive regenerate over the mergeb46d727e7
  • derive the registry dataset over the objects the last commits added2af35cbc3
  • derive the pages status over the inputs as they finally areced26b02c
  • derive regenerate over the merge, migrate one use case, renumber the ADR to 0016df138c2e5
  • derive the projections follow the strict gate onto the merged tree0169c885e
  • derive regenerate the projections after the rebasea70fdbc34
  • derive the site dataset and the formatting the rebase left behinde08bfcc77
  • derive regenerate over the merged session work6a584e688
  • derive the projections follow the tree, so the site can publish againd4e0ed7fb
  • derive regenerate after the merges, so the publication path accepts the tree0d9c347b3
  • derive the registry over the tree master merged into86ce0e7d8
  • derive the site dataset follows the rebased tree44d2806a6
  • derive the registry regenerated over the rebased tree6a585031e
  • sessions the episodes that built this, closed by the events they added921ab6b16
  • derive regenerate over the merge129bfe1a8
  • derive settle the mirrored status page7da59b1c1
  • derive regenerate over the merged treee17a73ead
  • derive regenerate over the merged treed847b3226
  • derive regenerate every derived artifact after the session lifecycle landedc852dea59
  • derive every projection regenerated from the merged tree62b71b3b6
  • site the plan projection follows the two new milestones73e76c1f1
  • derive the second pass the index needs after the first4658856fe
  • derive regenerate every projection over the merged tree235c47106
  • derive the projections follow the web command and its reports56372e100
  • web the generated web root is ignored, like every other derived tree9bb67d64c
  • site the website follows the registry and the docs index, regeneratedef755d41c
  • cockpit vendor the module build the page actually loads, and the dataset0d26ed9c5
  • derive the site dataset follows the two assertions that movedeaad9f682
  • derive one registry for one tree, at the tip9e224d050
  • derive regenerate the projections this branch owns, from a clean tree53b1d1c6c
  • derive the pages-status stamp, current with the inputs it was computed overde48006e3
  • derive regenerate over the decision subsystem and its two use casesbc32cac72
  • derive the pages-status page, current with the document it projectseba8bdbda
  • derive regenerate for the generator and performance-doc changedefed0c27
  • derive regenerate after integrating the prompt capturea0ccbc9e2
  • derive regenerate the derived artifacts over the integrated tree8cab3ebcf
  • derive regenerate the derived artifacts after merging the Pages fast path8e14274b6
  • derive regenerate the registry dataset over the tracked tree02b2e3e9f
  • derive regenerate for the third skill and the skills use caseef2136dc3
  • derive regenerate the site data and the registry dataset for the two skills9525f6280
  • site regenerate the derived data for the hero branch2cdc96310
  • derive regenerate on the merged treefa9db2be4
  • derive regenerate the registry dataset after the usecase library changec06271f54
  • derive regenerate on the merged treee90b347f0
  • derive regenerate every projection and the site data on the merged tree629ebf8a3
  • derive regenerate after merging PR #38 onto the scope policy31acaf90d
  • derive regenerate the projections, the OpenAPI document and the site data after the mergese31aceb75
  • derive regenerate the registry dataset and the site data after rebasing onto 4bbd72655452d619
  • derive regenerate the site data and the registry dataset after merging PR #304bbd7266d
  • bench re-record the macos-aarch64-debug baseline with its host (Apple M5 Pro/18)5f538d4c7
  • derive regenerate the derived data after merging origin/master32f796175
  • derive regenerate the site data and the registry dataset after rebasing onto 0481024b1be56192
  • site-data regenerate after the case 65 change1282a3630
  • derive regenerate the site data and the registry dataset after rebasing onto 77e28a804221ad38
  • derive regenerate the site data and the registry dataset after rebasing onto b9f1091080adee37
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc625b845f33a
  • site regenerate the registry dataset after its own claim joined the index24bb212a2
  • site-data regenerate after the test-case change0bf5f316d
  • derive regenerate the derived data after integrating PR #30, #31, #32 and #335b0e3e807
  • derive regenerate the site data and the registry dataset after rebasing onto b9f10914656b0be5
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc6281921eec1
  • site regenerate the registry dataset after its own claim joined the index5afb9bf57
  • bench re-record the macos-aarch64-debug baseline with its host (Apple M5 Pro/18)ff078af73
  • site-data regenerate for the case 28 probe changeb9f109147
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc62614b7b13a
  • site regenerate the registry dataset after its own claim joined the index1b017bad4
  • site-data regenerate the derived data after merging feature/mcp-shared-servercb9dc62b1
  • bench record the macos-aarch64-debug baseline from a clean tree at 1acda1d65ccf7835
  • projections restamp AGENTS.md and CLAUDE.md for the merged policy38093b339
  • generated regenerate the reference, the registry manifest and the site data after the merges08a235cf6
  • site-data regenerate after rebasing onto the merged Rust CLIda14b6414
  • site-data regenerate the plan status after the rebase onto master9d6339b14
  • site-data regenerate after the context claims and rule joined the inputs5e10fda21
  • rules a maintainer entry point for the shipped package manifestcbce33c79
  • site-data regenerate after the layer responsibility change6aba73108
  • rules wire the layer's claims into the rules that back theme2406d9cb
  • state close the plan-page task and start the .ai transformation task6d3b73b2e
  • state checkpoint that v0.1.0 is taggede85269422
  • site-data regenerate source.json at the checkpoint commitaabee071b
  • state checkpoint the responsibilities and argv work31f8b7bdc
  • state record why the enforcement gap was taken outside the plan29a5879ef
  • gitignore ignore local scratch directoriesca66fca22
  • state close the stale-base task and reopen at the current commit7ba86aeb8
  • site-data regenerate after RESPONSIBILITIES.yaml joined the inputsd6aca744e
  • state session records for the derived-plan-page task31965b1dc
  • site regenerate derived data after merging master07a71d563
  • site regenerate derived data after merging mastere792ebe8a
  • site regenerate after merging the doctrine brancha726e3cfc
  • site regenerate derived data after merging master94d2180ad
  • site regenerate after the merge5ea2fa7ec
  • site regenerate the derived data after merging master8c26a8e72
  • plan the suite evidence cites the run that covers every case40b6f3bfd
    I0010 Behavioural tests for schema, status, graph and command M000 Milestone and DAG driven development
  • site regenerate after the self-derivation and shellcheck fixes252a0dab2
  • site regenerate the derived data after merging the plan work99053b8c1
  • site regenerate derived data after the rebase7e88948fe
  • state checkpoint at the end of M0006563fc4a3
    M000 Milestone and DAG driven development
  • state the merge brought .gitignore into this task's diff rangeee0a12849
  • state close the stale-base task and start again at the current commit615c2b298
  • state widen the task scope to the projection targets and the README2dd5915d6
  • site regenerate after rebasee818a9d5e
  • site regenerate after rebase; new claims landed upstreama785baef2
  • state the audit task was scoped for writing, not for finding1555bf5b7
  • state close the worktree-ownership task; its base predates a peer's commits1e2bcfe50
  • state close the active task; it was gating other worktreesd95773ad7
  • state record the scope violation and the task that follows itbeb7b074c
  • site regenerate derived site data after the rebase477239041
# Formatting style 6
  • rust the crate is formatted as rustfmt wants it, and the projections follow7515a2b49
  • rust the crate is formatted, so the rust gate can fail for a reason5ae59e5fc
  • rust cargo fmt over the integrated tree, and the scope fixture's own limit1dbacfeb2
  • rust the crate is formatted as rustfmt wants itfead190a1
  • rust cargo fmt over the merged tree088ba7c86
  • tests one line rustfmt rewraps, so the rust gate can reach the rest6a2509c21
# Housekeeping chore 153
  • release 0.3.1, the version the fixed pipeline releases032cc0025
  • derive the projections follow the merges1fd5e32e0
  • derive the projections follow the merge with master748de838d
  • derive the claim is an object of the index once it is tracked3d649ae3b
  • derive the projections follow the gate and the versionfb5bbeb01
  • derive the projections follow the merges51a39cacc
  • derive the projections follow the fold89aec9654
  • derive the projections follow the mergesf9a1a4482
  • derive the projections follow the merged treeeac7c97ba
  • derive the projections follow the merge of masterdb64b42bf
  • derive the projections follow the merge of mastera568ee4c4
  • derive the projections follow the rebase onto masterdfcc21f19
  • sessions record two feature/ai-artifacts episodesbfffc0b1f
  • derive the projections follow the merge with master4bca63379
  • derive every projection regenerated over the integrated treec83f763fb
  • derive the projections follow the merged tree347c94342
  • sessions record two feature/ai-artifacts episodesc027ef6ea
  • plan I1003 done, with the evidence the contract asked for701d3780c
    I1003 Skills, rules, decisions, documents, use cases and benchmarks enter the graph as themselves
  • plan I1025 done, with the evidence the contract asked fora1fc8d8ac
    I1025 The federated model and its two projections are an architecture decision
  • plan I1004 done, with the evidence the contract asked for5b817c2eb
    I1004 Availability and visibility are metadata, not conditions in a template
  • plan I1002 done, with the evidence the contract asked for46da8089d
    I1002 Relations are typed, inferred from stable identities, and never dangle
  • derive the plan projection follows the two new milestones72544e632
  • derive the projections follow the capture fixes3fa38210f
  • plan I1001 done, with the evidence the contract asked fora4979a09b
    I1001 One typed graph composes the registries that already own their facts
  • derive the projections follow the merge with master988e928ee
  • derive every projection regenerated over the merge5961be109
  • derive every projection regenerated over the mergebb93f91d8
  • derive the site registry settlesedba7a9c5
  • derive the projections follow the rebase onto master730f4b167
  • derive every projection regenerated over the merge5ba3d60b6
  • derive the site registry follows the tree1f7955968
  • derive the mirrored status page settles on the second pass67a17cea1
  • derive the site follows the ported schema and the use case33fca6129
  • derive regenerate the projections after the rebase305b7f743
  • derive the registry dataset over the capture fix5d0e628ef
  • derive the registry dataset over the objects the last commits addedb3d05ae1d
  • derive the pages status over the inputs as they finally area2bb43fca
  • derive the site dataset and the formatting the rebase left behind4137b87bc
  • derive the registry over the tree master merged into0a13b50e3
  • derive the site dataset follows the rebased treec79b16c6e
  • derive the registry regenerated over the rebased tree32572bc9f
  • sessions the episodes that built this, closed by the events they addedacb0c173a
  • derive regenerate after rebasing the claim onto master0b0c104ba
  • derive the site registry follows the treec7f35c23c
  • derive the mirrored status page settles on the second passae4072bbc
  • derive the site follows the ported schema and the use case12668bb7b
  • derive regenerate the projections after the rebase42319a792
  • derive regenerate over the mergeb46d727e7
  • derive the registry dataset over the objects the last commits added2af35cbc3
  • derive the pages status over the inputs as they finally areced26b02c
  • derive regenerate over the merge, migrate one use case, renumber the ADR to 0016df138c2e5
  • derive the projections follow the strict gate onto the merged tree0169c885e
  • derive regenerate the projections after the rebasea70fdbc34
  • derive the site dataset and the formatting the rebase left behinde08bfcc77
  • derive regenerate over the merged session work6a584e688
  • derive the projections follow the tree, so the site can publish againd4e0ed7fb
  • derive regenerate after the merges, so the publication path accepts the tree0d9c347b3
  • derive the registry over the tree master merged into86ce0e7d8
  • derive the site dataset follows the rebased tree44d2806a6
  • derive the registry regenerated over the rebased tree6a585031e
  • sessions the episodes that built this, closed by the events they added921ab6b16
  • derive regenerate over the merge129bfe1a8
  • derive settle the mirrored status page7da59b1c1
  • derive regenerate over the merged treee17a73ead
  • derive regenerate over the merged treed847b3226
  • derive regenerate every derived artifact after the session lifecycle landedc852dea59
  • derive every projection regenerated from the merged tree62b71b3b6
  • site the plan projection follows the two new milestones73e76c1f1
  • derive the second pass the index needs after the first4658856fe
  • derive regenerate every projection over the merged tree235c47106
  • derive the projections follow the web command and its reports56372e100
  • web the generated web root is ignored, like every other derived tree9bb67d64c
  • site the website follows the registry and the docs index, regeneratedef755d41c
  • cockpit vendor the module build the page actually loads, and the dataset0d26ed9c5
  • derive the site dataset follows the two assertions that movedeaad9f682
  • derive one registry for one tree, at the tip9e224d050
  • derive regenerate the projections this branch owns, from a clean tree53b1d1c6c
  • derive the pages-status stamp, current with the inputs it was computed overde48006e3
  • derive regenerate over the decision subsystem and its two use casesbc32cac72
  • derive the pages-status page, current with the document it projectseba8bdbda
  • derive regenerate for the generator and performance-doc changedefed0c27
  • derive regenerate after integrating the prompt capturea0ccbc9e2
  • derive regenerate the derived artifacts over the integrated tree8cab3ebcf
  • derive regenerate the derived artifacts after merging the Pages fast path8e14274b6
  • derive regenerate the registry dataset over the tracked tree02b2e3e9f
  • derive regenerate for the third skill and the skills use caseef2136dc3
  • derive regenerate the site data and the registry dataset for the two skills9525f6280
  • site regenerate the derived data for the hero branch2cdc96310
  • derive regenerate on the merged treefa9db2be4
  • derive regenerate the registry dataset after the usecase library changec06271f54
  • derive regenerate on the merged treee90b347f0
  • derive regenerate every projection and the site data on the merged tree629ebf8a3
  • derive regenerate after merging PR #38 onto the scope policy31acaf90d
  • derive regenerate the projections, the OpenAPI document and the site data after the mergese31aceb75
  • derive regenerate the registry dataset and the site data after rebasing onto 4bbd72655452d619
  • derive regenerate the site data and the registry dataset after merging PR #304bbd7266d
  • bench re-record the macos-aarch64-debug baseline with its host (Apple M5 Pro/18)5f538d4c7
  • derive regenerate the derived data after merging origin/master32f796175
  • derive regenerate the site data and the registry dataset after rebasing onto 0481024b1be56192
  • site-data regenerate after the case 65 change1282a3630
  • derive regenerate the site data and the registry dataset after rebasing onto 77e28a804221ad38
  • derive regenerate the site data and the registry dataset after rebasing onto b9f1091080adee37
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc625b845f33a
  • site regenerate the registry dataset after its own claim joined the index24bb212a2
  • site-data regenerate after the test-case change0bf5f316d
  • derive regenerate the derived data after integrating PR #30, #31, #32 and #335b0e3e807
  • derive regenerate the site data and the registry dataset after rebasing onto b9f10914656b0be5
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc6281921eec1
  • site regenerate the registry dataset after its own claim joined the index5afb9bf57
  • bench re-record the macos-aarch64-debug baseline with its host (Apple M5 Pro/18)ff078af73
  • site-data regenerate for the case 28 probe changeb9f109147
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc62614b7b13a
  • site regenerate the registry dataset after its own claim joined the index1b017bad4
  • site-data regenerate the derived data after merging feature/mcp-shared-servercb9dc62b1
  • bench record the macos-aarch64-debug baseline from a clean tree at 1acda1d65ccf7835
  • projections restamp AGENTS.md and CLAUDE.md for the merged policy38093b339
  • generated regenerate the reference, the registry manifest and the site data after the merges08a235cf6
  • site-data regenerate after rebasing onto the merged Rust CLIda14b6414
  • site-data regenerate the plan status after the rebase onto master9d6339b14
  • site-data regenerate after the context claims and rule joined the inputs5e10fda21
  • rules a maintainer entry point for the shipped package manifestcbce33c79
  • site-data regenerate after the layer responsibility change6aba73108
  • rules wire the layer's claims into the rules that back theme2406d9cb
  • state close the plan-page task and start the .ai transformation task6d3b73b2e
  • state checkpoint that v0.1.0 is taggede85269422
  • site-data regenerate source.json at the checkpoint commitaabee071b
  • state checkpoint the responsibilities and argv work31f8b7bdc
  • state record why the enforcement gap was taken outside the plan29a5879ef
  • gitignore ignore local scratch directoriesca66fca22
  • state close the stale-base task and reopen at the current commit7ba86aeb8
  • site-data regenerate after RESPONSIBILITIES.yaml joined the inputsd6aca744e
  • state session records for the derived-plan-page task31965b1dc
  • site regenerate derived data after merging master07a71d563
  • site regenerate derived data after merging mastere792ebe8a
  • site regenerate after merging the doctrine brancha726e3cfc
  • site regenerate derived data after merging master94d2180ad
  • site regenerate after the merge5ea2fa7ec
  • site regenerate the derived data after merging master8c26a8e72
  • plan the suite evidence cites the run that covers every case40b6f3bfd
    I0010 Behavioural tests for schema, status, graph and command M000 Milestone and DAG driven development
  • site regenerate after the self-derivation and shellcheck fixes252a0dab2
  • site regenerate the derived data after merging the plan work99053b8c1
  • site regenerate derived data after the rebase7e88948fe
  • state checkpoint at the end of M0006563fc4a3
    M000 Milestone and DAG driven development
  • state the merge brought .gitignore into this task's diff rangeee0a12849
  • state close the stale-base task and start again at the current commit615c2b298
  • state widen the task scope to the projection targets and the README2dd5915d6
  • site regenerate after rebasee818a9d5e
  • site regenerate after rebase; new claims landed upstreama785baef2
  • state the audit task was scoped for writing, not for finding1555bf5b7
  • state close the worktree-ownership task; its base predates a peer's commits1e2bcfe50
  • state close the active task; it was gating other worktreesd95773ad7
  • state record the scope violation and the task that follows itbeb7b074c
  • site regenerate derived site data after the rebase477239041
# Formatting style 6
  • rust the crate is formatted as rustfmt wants it, and the projections follow7515a2b49
  • rust the crate is formatted, so the rust gate can fail for a reason5ae59e5fc
  • rust cargo fmt over the integrated tree, and the scope fixture's own limit1dbacfeb2
  • rust the crate is formatted as rustfmt wants itfead190a1
  • rust cargo fmt over the merged tree088ba7c86
  • tests one line rustfmt rewraps, so the rust gate can reach the rest6a2509c21
# Housekeeping chore 153
  • release 0.3.1, the version the fixed pipeline releases032cc0025
  • derive the projections follow the merges1fd5e32e0
  • derive the projections follow the merge with master748de838d
  • derive the claim is an object of the index once it is tracked3d649ae3b
  • derive the projections follow the gate and the versionfb5bbeb01
  • derive the projections follow the merges51a39cacc
  • derive the projections follow the fold89aec9654
  • derive the projections follow the mergesf9a1a4482
  • derive the projections follow the merged treeeac7c97ba
  • derive the projections follow the merge of masterdb64b42bf
  • derive the projections follow the merge of mastera568ee4c4
  • derive the projections follow the rebase onto masterdfcc21f19
  • sessions record two feature/ai-artifacts episodesbfffc0b1f
  • derive the projections follow the merge with master4bca63379
  • derive every projection regenerated over the integrated treec83f763fb
  • derive the projections follow the merged tree347c94342
  • sessions record two feature/ai-artifacts episodesc027ef6ea
  • plan I1003 done, with the evidence the contract asked for701d3780c
    I1003 Skills, rules, decisions, documents, use cases and benchmarks enter the graph as themselves
  • plan I1025 done, with the evidence the contract asked fora1fc8d8ac
    I1025 The federated model and its two projections are an architecture decision
  • plan I1004 done, with the evidence the contract asked for5b817c2eb
    I1004 Availability and visibility are metadata, not conditions in a template
  • plan I1002 done, with the evidence the contract asked for46da8089d
    I1002 Relations are typed, inferred from stable identities, and never dangle
  • derive the plan projection follows the two new milestones72544e632
  • derive the projections follow the capture fixes3fa38210f
  • plan I1001 done, with the evidence the contract asked fora4979a09b
    I1001 One typed graph composes the registries that already own their facts
  • derive the projections follow the merge with master988e928ee
  • derive every projection regenerated over the merge5961be109
  • derive every projection regenerated over the mergebb93f91d8
  • derive the site registry settlesedba7a9c5
  • derive the projections follow the rebase onto master730f4b167
  • derive every projection regenerated over the merge5ba3d60b6
  • derive the site registry follows the tree1f7955968
  • derive the mirrored status page settles on the second pass67a17cea1
  • derive the site follows the ported schema and the use case33fca6129
  • derive regenerate the projections after the rebase305b7f743
  • derive the registry dataset over the capture fix5d0e628ef
  • derive the registry dataset over the objects the last commits addedb3d05ae1d
  • derive the pages status over the inputs as they finally area2bb43fca
  • derive the site dataset and the formatting the rebase left behind4137b87bc
  • derive the registry over the tree master merged into0a13b50e3
  • derive the site dataset follows the rebased treec79b16c6e
  • derive the registry regenerated over the rebased tree32572bc9f
  • sessions the episodes that built this, closed by the events they addedacb0c173a
  • derive regenerate after rebasing the claim onto master0b0c104ba
  • derive the site registry follows the treec7f35c23c
  • derive the mirrored status page settles on the second passae4072bbc
  • derive the site follows the ported schema and the use case12668bb7b
  • derive regenerate the projections after the rebase42319a792
  • derive regenerate over the mergeb46d727e7
  • derive the registry dataset over the objects the last commits added2af35cbc3
  • derive the pages status over the inputs as they finally areced26b02c
  • derive regenerate over the merge, migrate one use case, renumber the ADR to 0016df138c2e5
  • derive the projections follow the strict gate onto the merged tree0169c885e
  • derive regenerate the projections after the rebasea70fdbc34
  • derive the site dataset and the formatting the rebase left behinde08bfcc77
  • derive regenerate over the merged session work6a584e688
  • derive the projections follow the tree, so the site can publish againd4e0ed7fb
  • derive regenerate after the merges, so the publication path accepts the tree0d9c347b3
  • derive the registry over the tree master merged into86ce0e7d8
  • derive the site dataset follows the rebased tree44d2806a6
  • derive the registry regenerated over the rebased tree6a585031e
  • sessions the episodes that built this, closed by the events they added921ab6b16
  • derive regenerate over the merge129bfe1a8
  • derive settle the mirrored status page7da59b1c1
  • derive regenerate over the merged treee17a73ead
  • derive regenerate over the merged treed847b3226
  • derive regenerate every derived artifact after the session lifecycle landedc852dea59
  • derive every projection regenerated from the merged tree62b71b3b6
  • site the plan projection follows the two new milestones73e76c1f1
  • derive the second pass the index needs after the first4658856fe
  • derive regenerate every projection over the merged tree235c47106
  • derive the projections follow the web command and its reports56372e100
  • web the generated web root is ignored, like every other derived tree9bb67d64c
  • site the website follows the registry and the docs index, regeneratedef755d41c
  • cockpit vendor the module build the page actually loads, and the dataset0d26ed9c5
  • derive the site dataset follows the two assertions that movedeaad9f682
  • derive one registry for one tree, at the tip9e224d050
  • derive regenerate the projections this branch owns, from a clean tree53b1d1c6c
  • derive the pages-status stamp, current with the inputs it was computed overde48006e3
  • derive regenerate over the decision subsystem and its two use casesbc32cac72
  • derive the pages-status page, current with the document it projectseba8bdbda
  • derive regenerate for the generator and performance-doc changedefed0c27
  • derive regenerate after integrating the prompt capturea0ccbc9e2
  • derive regenerate the derived artifacts over the integrated tree8cab3ebcf
  • derive regenerate the derived artifacts after merging the Pages fast path8e14274b6
  • derive regenerate the registry dataset over the tracked tree02b2e3e9f
  • derive regenerate for the third skill and the skills use caseef2136dc3
  • derive regenerate the site data and the registry dataset for the two skills9525f6280
  • site regenerate the derived data for the hero branch2cdc96310
  • derive regenerate on the merged treefa9db2be4
  • derive regenerate the registry dataset after the usecase library changec06271f54
  • derive regenerate on the merged treee90b347f0
  • derive regenerate every projection and the site data on the merged tree629ebf8a3
  • derive regenerate after merging PR #38 onto the scope policy31acaf90d
  • derive regenerate the projections, the OpenAPI document and the site data after the mergese31aceb75
  • derive regenerate the registry dataset and the site data after rebasing onto 4bbd72655452d619
  • derive regenerate the site data and the registry dataset after merging PR #304bbd7266d
  • bench re-record the macos-aarch64-debug baseline with its host (Apple M5 Pro/18)5f538d4c7
  • derive regenerate the derived data after merging origin/master32f796175
  • derive regenerate the site data and the registry dataset after rebasing onto 0481024b1be56192
  • site-data regenerate after the case 65 change1282a3630
  • derive regenerate the site data and the registry dataset after rebasing onto 77e28a804221ad38
  • derive regenerate the site data and the registry dataset after rebasing onto b9f1091080adee37
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc625b845f33a
  • site regenerate the registry dataset after its own claim joined the index24bb212a2
  • site-data regenerate after the test-case change0bf5f316d
  • derive regenerate the derived data after integrating PR #30, #31, #32 and #335b0e3e807
  • derive regenerate the site data and the registry dataset after rebasing onto b9f10914656b0be5
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc6281921eec1
  • site regenerate the registry dataset after its own claim joined the index5afb9bf57
  • bench re-record the macos-aarch64-debug baseline with its host (Apple M5 Pro/18)ff078af73
  • site-data regenerate for the case 28 probe changeb9f109147
  • derive regenerate the site data and the registry dataset after rebasing onto cb9dc62614b7b13a
  • site regenerate the registry dataset after its own claim joined the index1b017bad4
  • site-data regenerate the derived data after merging feature/mcp-shared-servercb9dc62b1
  • bench record the macos-aarch64-debug baseline from a clean tree at 1acda1d65ccf7835
  • projections restamp AGENTS.md and CLAUDE.md for the merged policy38093b339
  • generated regenerate the reference, the registry manifest and the site data after the merges08a235cf6
  • site-data regenerate after rebasing onto the merged Rust CLIda14b6414
  • site-data regenerate the plan status after the rebase onto master9d6339b14
  • site-data regenerate after the context claims and rule joined the inputs5e10fda21
  • rules a maintainer entry point for the shipped package manifestcbce33c79
  • site-data regenerate after the layer responsibility change6aba73108
  • rules wire the layer's claims into the rules that back theme2406d9cb
  • state close the plan-page task and start the .ai transformation task6d3b73b2e
  • state checkpoint that v0.1.0 is taggede85269422
  • site-data regenerate source.json at the checkpoint commitaabee071b
  • state checkpoint the responsibilities and argv work31f8b7bdc
  • state record why the enforcement gap was taken outside the plan29a5879ef
  • gitignore ignore local scratch directoriesca66fca22
  • state close the stale-base task and reopen at the current commit7ba86aeb8
  • site-data regenerate after RESPONSIBILITIES.yaml joined the inputsd6aca744e
  • state session records for the derived-plan-page task31965b1dc
  • site regenerate derived data after merging master07a71d563
  • site regenerate derived data after merging mastere792ebe8a
  • site regenerate after merging the doctrine brancha726e3cfc
  • site regenerate derived data after merging master94d2180ad
  • site regenerate after the merge5ea2fa7ec
  • site regenerate the derived data after merging master8c26a8e72
  • plan the suite evidence cites the run that covers every case40b6f3bfd
    I0010 Behavioural tests for schema, status, graph and command M000 Milestone and DAG driven development
  • site regenerate after the self-derivation and shellcheck fixes252a0dab2
  • site regenerate the derived data after merging the plan work99053b8c1
  • site regenerate derived data after the rebase7e88948fe
  • state checkpoint at the end of M0006563fc4a3
    M000 Milestone and DAG driven development
  • state the merge brought .gitignore into this task's diff rangeee0a12849
  • state close the stale-base task and start again at the current commit615c2b298
  • state widen the task scope to the projection targets and the README2dd5915d6
  • site regenerate after rebasee818a9d5e
  • site regenerate after rebase; new claims landed upstreama785baef2
  • state the audit task was scoped for writing, not for finding1555bf5b7
  • state close the worktree-ownership task; its base predates a peer's commits1e2bcfe50
  • state close the active task; it was gating other worktreesd95773ad7
  • state record the scope violation and the task that follows itbeb7b074c
  • site regenerate derived site data after the rebase477239041
# Other other 5
  • cockpit wip: the legibility work as the working tree held it643e75ea2
  • Merge origin/master into fix/home-path-gated63e2467d
  • Merge origin/master into fix/derived-merge-driver-enforcede37f21a03
  • merge: the rule, the case, the base-path gate and the generated route reference90ec4556c
  • merge: the contract-working hero99b117832

Published

What this version put on the release, with the digest the record read off each file. The installer resolves the same names.

targetfilesha256
macos-aarch64 majordomus-v0.3.1-aarch64-apple-darwin.tar.gz 549269f08e9f2f1d53173f72d8c86caecc39526fd53a42ae547c1adeaaba6d58
macos-x86_64 majordomus-v0.3.1-x86_64-apple-darwin.tar.gz 084a5956f06c4d5934b9161a179f1a0aafe16b3edbf14651cf3af2ee80dbfcbd
linux-x86_64-gnu majordomus-v0.3.1-x86_64-unknown-linux-gnu.tar.gz d4b34c5efeab749bfd7187d5fc47880d3056594cbe35e703797aa5ed8630f0f9
linux-x86_64-musl majordomus-v0.3.1-x86_64-unknown-linux-musl.tar.gz 504f168f868cca99aec018242480cafe468f7d3b4e6ca1e58e48d930b863eb12
linux-aarch64-gnu majordomus-v0.3.1-aarch64-unknown-linux-gnu.tar.gz 6e7d865c6b4c540c7e12b985cfc04cda7fc6250527b193d0e187677439d4ab50
linux-aarch64-musl majordomus-v0.3.1-aarch64-unknown-linux-musl.tar.gz 6ca046c0dd7061826232d6e67d3380aee573bd4ee9cb09d58430e38f722da836