What is ready, and what it was measured against
A release here is a record of readiness, not a deployment. Every release check below is measured against this database at the moment somebody asks — a release nobody can re-measure is a promise, not a fact.
The last release
No dataNo release has been recorded yet.What it was measured against
A blocking release check stops the release. An advisory one reports and does not stop it, and says why it does not.
Nothing has been recorded here yet.
This map holds only what has been read and checked against a source, and nothing has been recorded for this section. Empty here means exactly that — not zero, and not a fault in the page.
The release being prepared
Measured against the same release checks, and not out. What blocks it is named below rather than left to be discovered on the day.
v0.1.0
Blocked
The first declared release of the private preview: what the corpus, the map and the control route measure as they stand, and which gates that measurement does not pass.
This release is not going out. What stopped it is above, named. The reference numbers reproduce — all three reference numbers of the methodology are produced by the engine — measured 0. the engine reproduces 0 of the 3 reference values, recomputed from the canon rather than stored
| Release check | Outcome | Measured | What it has to be | Why this is a release check |
|---|---|---|---|---|
| The changelog stands on records (blocking) | Not applicable | 0 | every changelog entry stands on a record that is there | What a reader is told about a change has to be checkable against the row that produced it. An entry standing on nothing is prose, and prose about evidence is what this project exists not to publish. |
| Every stop names its reason (blocking) | Passed | 0 | every stopped piece of work names its reason | A halted queue nobody can read is the failure M11 exists to remove. Releasing with one in it hands an operator a system they cannot answer questions about. |
| Milestones are consistent (blocking) | Passed | 0 | one milestone in flight at a time, and nothing accepted over one that was never started | The programme rule is one milestone in flight at a time and no leapfrogging. A checklist can drift from that quietly; a gate cannot. |
| No science finishes without a person (blocking) | Passed | 0 | no scientific work finished without reaching a person | The machine proposes. Work whose output is a scientific statement that finished on its own means the boundary of M11 was crossed somewhere, and a release would carry that across. |
| No work past its deadline (blocking) | Passed | 0 | nothing unfinished is past its deadline | Work past its deadline is either stuck or lying about being alive. Either way it is not a state to freeze a release on top of. |
| Records declare their corpus (blocking) | Passed | 0 | every published document says which corpus it belongs to | This canon holds real records and records written to validate the methodology. A document that does not say which it is turns synthetic material into apparent literature the moment it is read. |
| The reference numbers reproduce (blocking) | Not passed | 0 | all three reference numbers of the methodology are produced by the engine | The methodology is validated against three numbers computed from the canon. If they no longer come out, what is being released is a different methodology wearing the same name. |
| Sources stand on a legal basis (blocking) | Not passed | 3 | no source is switched on without a live contract | A source that is enabled without a named legal basis can testify with nothing able to refuse it. The barrier used to ask for a contract, which three public sources will never sign, so its only true answer was no and its only green answer was a false one. It now asks the question that has an honest answer: on what basis, and which fields does that basis permit. |
| Who sees this is declared (blocking) | Passed | 0 | every role has a decision, with a reason, about seeing the machine queue | An absence and a decision look identical unless the decision is written down. A role nobody decided about is a question that will be answered by accident later. |
| The worker is declared (blocking) | Passed | 0 | exactly one runtime is declared, and every work type has a stance on it | D-16 says the worker lives in the same application. A work type nobody said anything about is one the runner might pick up — or silently never run — and both are decisions nobody took. |
| The human queue is within capacity (advisory) | Passed | 0 | work waiting for a person is within the declared capacity of 40 decisions (D-09) | This is ADVISORY and does not block: a queue of human decisions is a fact about people, not a defect in the product. It is reported because D-09 says the scarce thing is a person, and a release that quietly doubles that queue should be taken knowingly. |
Every release
| Release | State | Changes | What it is for |
|---|---|---|---|
| v0.1.0 | Blocked | 0 | The first declared release of the private preview: what the corpus, the map and the control route measure as they stand, and which gates that measurement does not pass. |
The background service, as described in advance
Decision D-16 in the decision register settled that the background job runs inside the same application. This repository says so and installs no background service: starting one is an operational decision, and hiding who took it would be the same failure this page exists to remove.
- Where it runs: In the same application as everything else, as a bounded run rather than a process that lives for ever.
- Who starts it: Operations, explicitly — a command, a scheduler or a person. This repository declares the runtime and does not install a daemon: starting one is an operational decision, and pretending otherwise would hide who made it.
- Why only one runs at a time: A Postgres advisory lock. A second runner finds it held, says so and exits, rather than doubling every claim.
- What bounds a run: A maximum number of tasks and a wall clock. A run stops at its bound, not when the queue happens to empty.
- The network: The network is not switched on in this repository. A live retrieval needs a legal basis on the source (M08) and an owner decision; until both exist, the runner executes only work it can do from records it already holds.
What it may execute
- Puts a disagreement between records in front of a curator. — The runner may prepare the question and hand it to a curator. It may not answer it: the finishing move here is a person, and the database refuses anything else.
- Puts a proposed scientific statement in front of a curator. Nothing here publishes by itself. — The same: a proposed scientific statement is put in front of a person. Nothing about it is published by a machine.
- Rebuilds the research opportunities after the evidence under them moved. — Rebuilding the opportunity board is whole-canon work this repository can do deterministically, and M10 already owns the mechanism it calls.
- Checks whether a paper this canon stands on has been retracted. — The retraction status is read from the record this canon already holds. No network is needed, and claiming a retrieval it never made would be worse than not running at all.
What waits, and why
- Checks that a source still answers in the shape we agreed with it. — Checking that a source still answers in the agreed shape requires fetching from it. The network is not switched on, so this work waits rather than pretending to have checked.
Where the product stands
One milestone is in flight at a time, and nothing is accepted over a milestone that was never started. Both are release checks above, not conventions.
| Milestone | State | Where the acceptance can be checked |
|---|---|---|
| M00 — Master Blueprint | Accepted | docs/REVIEW_PACKET_W2.md |
| M01 — Knowledge Core | Accepted | docs/REVIEW_PACKET_W2.md |
| M02 — Evidence Scoring and ClaimContext | Accepted | docs/REVIEW_PACKET_W2.md |
| M03 — Ingest, real corpus and curation | Accepted | docs/REVIEW_PACKET_W3.md |
| M04 — The public evidence map | Accepted | docs/REVIEW_PACKET_W4A.md |
| M05 — Intelligence | Accepted | docs/REVIEW_PACKET_W5.md |
| M06-A — Private profile and consent | Accepted | docs/REVIEW_PACKET_W6.md |
| M06-B — Seven functional domains | Accepted | docs/REVIEW_PACKET_W6B.md |
| M06-C — Longitudinal dynamics | Replaced | docs/REVIEW_PACKET_W6C.md |
| M06-C2 — One authoritative current value | Accepted | 3ae982e |
| M07 — Actor and Ecosystem Graph | Accepted | 3a614e4 |
| M08 — Global Source Federation | Accepted | 9ce9592 |
| M09 — Role Workspaces | Accepted | 972d43b |
| M10 — Matching and Opportunity Engine | Accepted | a691461 |
| M11 — Agent Orchestration and Continuous Watch | Accepted | 3c6eb6c |
| M12 — Release, Continuous Operations and Product Completion | Accepted | 3d91187 |