f9d6b57f0f
The docs lived on one lineage and the fleet code on another. That is why six pages described a shared fleet key as how an agent authenticates, why COLLECTOR-AUTH had to warn that the per-PC credential code was not in the repository it sat in, and why ADR-019 recorded a decision whose implementation was somewhere else. Documentation that cannot see the code it documents goes stale by construction, and no amount of editing fixes that. So the corpus moves here: 84 files, 56 pages, 20 ADRs, the proposals, INDEX.md, llms.txt and both gates. Filenames are unchanged, because a wiki page name is derived from the filename and a rename breaks every link anybody saved. THE POINT OF THE MOVE IS THE CORRECTION IT ENABLES. Every caveat that said "not in this tree" was false the moment the files landed beside the code, so each was rewritten from what is actually here: - COLLECTOR-AUTH gained the real enroll request body, the two bounds on the unauthenticated route (per-IP rate limit, pending cap with stale rows dropped before a real PC is refused), and the rejected pending reason that binds to the endpoint identity rather than the nonce. - ADR-019 now describes an implementation that is present, including its tests, and says plainly that what remains is the FLEET migration, not the code. - proposals/device-identity claimed phase 1 was unbuilt. plugins/computers declares deviceid on the collector schema and prefers it over the older fallbacks. Corrected in the page, its summary and the index. WINDOWS/IIS IS NOW DOCUMENTED AS THE LEGACY PATH, per the product decision, and carefully: it is what production runs today. Every Windows page opens by saying it is supported, not for a new site, and where a new site should go instead. No procedure was cut - an operator on an IIS box at 2am needs these pages to work exactly as well tomorrow. MIGRATE-TOPOLOGY stops being a footnote and becomes the off-ramp, which is why it nearly doubled: what was there did not match how the Docker stack really works here. The Docker material that already lived on this line was kept and given ownership rather than buried under the ported Windows-centric prose: DEPLOY now describes the four services, the migrate service that runs the upgrade chain before api starts, TLS terminated by nginx, and the plugin count corrected from thirteen to seventeen - a number both lineages had wrong. ROADMAP is rewritten from evidence rather than memory: what has shipped, read out of the changelog, the ADRs and the manifests, and ahead of it exactly two items - finalize a distributed release and polish the setup wizard. PROJECT-MAP is generated and was stale; the GENERATOR was what was wrong. --check passes now. API-REFERENCE is retired to a pointer. /api/docs serves 573 operations with derived auth, query parameters and harvested examples, and a hand-written page competing with that is a liability. The file stays so its wiki page and its inbound links survive. AND THE MOVE TURNED ON A SCRUB THAT HAD NEVER RUN HERE. test_docs_publishable keys on docs/*.md, which this line did not have, so it skipped - its own comment predicted what would surface. Porting the corpus activated it and it found 48 lines that must not reach a published wiki: branch names abbreviating the site, assistant-tooling paths, the site name in two deployment pages, and an employee ID in a Windows path that the scrub does not even look for.
1.9 KiB
1.9 KiB
Proposals
A proposal is a design written before the work, kept afterwards as the record of why the thing looks the way it does. A proposal is NOT a decision record: where a proposal and an ADR disagree, the ADR wins.
None of these is current guidance. Read one to understand why something exists, not to learn how it works today - for that, read the page named in the right-hand column.
| Proposal | What it designed | Built? | Read instead |
|---|---|---|---|
| dashboard-live-fleet | A dashboard that shows what needs doing instead of row counts | Yes | ADR-010 for the contract it introduced |
| device-identity | One durable identity for the device a PC drives, ending in the registry | Phase 1 built (the collector deviceid field). Phases 2 and 3 not started |
The proposal itself, for the remaining phases |
| ge-enforce-plugin | GE-Enforce manifests as ShopDB data, served over HTTP | Yes | ADR-012, then GE-ENFORCE |
| printedparts-plugin | A 3D-printed-parts storefront, bin labels and a kiosk | Yes, as plugins/printedparts/ |
PLUGIN-LAB-PRINTEDPARTS |
| printer-assignment | Printers as a property of the machine, installed by the PC | Yes, v0.11.3 and v0.12.0 | PRINTER-INSTALLER, COLLECTOR-INTEGRATION |
A proposal that is adopted says so in its own status line, and names what adopted it. A proposal nobody built stays here anyway: the alternatives it rejected are the part worth keeping.