| 2026-08-01 | REGISTER | DR-111 added (accepted) — Own SessionEnd hook replaces the plugin’s per-turn whole-slug mine; parent transcripts get exchange AND general, subagents exchange only; auto_save off takes the CHECKPOINT diary writes with it | 54715e7 |
| 2026-08-01 | REGISTER | DR-112 added (accepted) — Four tiers drive mine/don’t-mine, room routing and cadence; 839 paths are deleted before re-mining; the knowledge-graph verdict is deferred to a post-prune re-census rather than ruled now | 54715e7 |
| 2026-08-01 | REGISTER | DR-113 added (accepted) — DR-112’s T3 tier cannot be expressed as path-keyword room routing; the DR-106 stale families are discriminated at recall time from source_file, and a file’s room can only be changed by delete-then-re-mine | 04a9e9e |
| 2026-08-01 | REGISTER | DR-114 added (accepted) — Rooms may be declared priority with path carve-outs; that makes DR-112’s T3 stale-family tier expressible, so DR-113’s withdrawal is amended and Q4’s file move is withdrawn | b3002a3 |
| 2026-08-01 | REGISTER | DR-115 added (accepted) — The docs-site *.html mine exclusion carves out authored decision boards; rehoming a gitignored working artefact must be followed by a re-mine before its old drawers are pruned | 9611b56 |
| 2026-08-01 | REGISTER | DR-116 added (accepted) — Room keys must be directory names matched at any depth, never path positions, so a room survives the in-flight domain migration; and a room projection must re-implement detect_room from source rather than model it | 9611b56 |
| 2026-08-01 | REGISTER | DR-117 added (accepted) — The form-extraction templates settle at scripts/cocoindex_pipeline/fixtures/form-templates/, a sibling of platform-corpus/ — fixture trees are filed by the domain that owns them, never by the kind of artefact they are | 26542ed |
| 2026-08-02 | REGISTER | DR-118 added (accepted) — The cross-tree fixture register settles at docs/reference/testing/corpus-manifest.json — DR-117 files fixture TREES by owning domain, but a register spanning every tree has no owning domain, so it files as what it is: a testing standard | a42c358 |
| 2026-08-02 | REGISTER | DR-119 added (accepted) — The cocoindex image moves to a checked-in Dockerfile with a CI-generated linux-x86_64 lock installed —no-deps; the nightly stops building its own image and pulls the published one — retiring a Cloud-Run-era builder for a workload with no Google Cloud | 3f8d343 |
| 2026-08-02 | DEPLOY | the cocoindex nightly seeds and walks the vendored Platform corpus as its baseline via sync-platform-corpus.sh, and builds the same post-pack image recipe the platform deploys | 2f953e6 |
| 2026-08-02 | WORKFLOW | cocoindex integration tests import fixture paths from tests/integration/cocoindex/_helpers/fixtures.ts, which resolves them from the corpus manifest by id — never hardcode a fixture path | 2f953e6 |
| 2026-08-03 | REGISTER | DR-120 added (accepted) — The cocoindex nightly becomes the source of truth for the stage → walk → Vitest sequence and the on-prem live-verify.sh operator hook is DELETED, not reconciled — it had been unrunnable for months, so there was no working second copy to extract shared steps into | e700cfd |
| 2026-08-03 | REGISTER | DR-121 added (accepted) — taxonomy_snapshot.json moves to scripts/cocoindex_pipeline/data/ before id-416 narrows the build context — a file production reads at import time is not a test fixture, and the Dockerfile move would otherwise ship an image whose pipeline cannot start | e700cfd |
| 2026-08-03 | REGISTER | DR-122 added (accepted) — A room keyword that scores on detect_room’s substring pass is a latent orphan-plus-duplicate under DR-113, so keywords are compounded until they score ~0 at P3 while keeping their P0 reach; and the projection that proves it must import the real detect_room rather than re… | 95b282a |
| 2026-08-03 | REGISTER | DR-123 added (accepted) — DR-104 covered code and DR-106 covered stale docs; neither covered task files, which is precisely where the premises under investigation get written down — a task’s goal text, ACs, owner-directives and invariants record that someone decided, not that they re-derived, and… | 2e08b41 |
| 2026-08-03 | REGISTER | DR-124 added (accepted) — Closes id-364 F1: reference items and source documents are separate first-class entities and the discriminator is lifecycle, not identity — source documents are walked and reference items are not, so a reference item carries no walk cadence and needs no synthetic registe… | 2e08b41 |
| 2026-08-04 | REGISTER | DR-125 added (accepted) — Every promoted q_a_pair must carry a scope_tag, which makes the (primary_domain, primary_subtopic) topic-concept grain a transitional fallback whose requirement expires at first bundle publication — not a permanent part of the concept model | 7960818 |
| 2026-08-04 | REGISTER | DR-126 added (accepted) — Guides are concept-clusters whose skeleton (sections, names, order, nesting, is_required) is human-authored in the Platform DB and whose membership is producer-derived; guides/guide_sections stay DB tables because the bundle is a product of the curation loop and never an… | 7960818 |
| 2026-08-04 | REGISTER | DR-127 added (accepted) — /review becomes a single queue faceted publication | governance | freshness, each owner-kind-polymorphic where its axis is, absorbing /api/governance/review and /promotion-gate; the quality score retires and its level-triggered backstop moves to the freshness axis | 7960818 |
| 2026-08-04 | SCHEMA | new migration 20260804143712_id417_ddl_retire_change_reports_disputes_coverage.sql — feat(id-417): the coordinated DDL pass — drop change_reports, classification_disputes, coverage_targets | 6bcd9f6 |
| 2026-08-04 | REGISTER | DR-128 added (accepted) — The tool lives at ai-solution-hub/ast-dataflow (public); canonical installs it as a bun git dependency pinned to a SHA and registers the MCP server in .mcp.json — executing DR-100’s extraction rider. npm publish is deferred, not rejected. | 4f7ce65 |
| 2026-08-04 | REGISTER | DR-129 added (accepted) — Public-facing ast-dataflow documentation is authored fresh in the tool repo from measured shipped behaviour; docs-site ledger artefacts stay private and never migrate as files. Anything crossing the private→public boundary needs a token scrub plus owner PR review. | e1c7fee |
| 2026-08-05 | SCHEMA | new migration 20260805131542_id382_writer_fence_lease_renew.sql — feat(id-382): corpus_writer_fence_lease_renew RPC + api wrapper + types regen | 4e721a1 |
| 2026-08-05 | SCHEMA | new migration 20260805115054_id416_drop_taxonomy_sync_state.sql — chore(id-416): retire taxonomy-sync machinery — workflow, dispatcher, sync-state table | 29f0cdf |
| 2026-08-05 | REGISTER | DR-121 status accepted → superseded | a1701b2 |
| 2026-08-05 | REGISTER | DR-130 added (accepted) — Owner-ratified target shape: nothing is driven by a platform-global subject vocabulary; the 7×34 domains/subtopics retire as a platform-core concept, taxonomy_snapshot.json retires entirely (superseding DR-121’s move), and any future client subject vocabulary returns as … | a1701b2 |
| 2026-08-05 | WORKFLOW | dispatch briefs must name a concept’s origin and treat assumption-era docs as carriers, not evidence | ac16909 |
| 2026-08-05 | WORKFLOW | the PostToolUse prettier hook formats only files inside the session’s own project | f78b0ff |
| 2026-08-06 | SCHEMA | new migration 20260805190000_id417_dr130_sd_ri_taxonomy_retirement.sql — feat(id-417): DR-130/DR-124 DDL — retire sd/ri subject-taxonomy columns, taxonomy tables, sd-mint unwind | 19ca259 |
| 2026-08-06 | REGISTER | DR-131 added (accepted) — Extends DR-096’s local-stack substrate from the E2E lanes to both integration lanes, and adds a suite-boundary interlock refusing any non-loopback host — after an unattended CI job fired the authoritative knowledge-admission gate against shared staging and left 88 mock p… | 7db3fa9 |
| 2026-08-06 | REGISTER | DR-132 added (accepted) — Reference items are external references — citable evidence, never authoritative alone. They need no knowledge-admission gate (superseded_by is the whole lifecycle), and they are not a form-matching corpus, which retires id-131 BI-29’s reference_items lane as an unwanted … | 997e6d8 |
| 2026-08-08 | REGISTER | DR-133 added (accepted) — An integration fixture staged under a per-test prefix must carry bytes distinct from every walked-baseline document: content-hash-first identity makes a byte-identical re-stage resolve onto the baseline row, and because that resolve rewrites logical_path but never filena… | b6d5cb8 |
| 2026-08-08 | REGISTER | DR-134 added (accepted) — The RSS feed routes move under the intelligence namespace and gain workspace-scoped feed tokens carried in the URL; session auth would make the feature unusable by its only consumers, and header auth is bypassable because these are the only two API routes emitting a shar… | f7119d8 |
| 2026-08-09 | REGISTER | DR-135 added (accepted) — An entity_mentions row whose surface form does not occur in its document’s content_text carries no context_snippet, therefore no evidence the document was read, therefore no citable provenance — so the pipeline refuses the row rather than writing it empty | 95221d2 |
| 2026-08-09 | REGISTER | DR-136 added (accepted) — A knip unused-export finding is resolved by wiring, un-exporting or deleting the symbol; @public asserts deliberate library surface and may only be applied where that assertion is true, which a server-only module can never satisfy | 7fbf8aa |
| 2026-08-09 | REGISTER | DR-137 added (accepted) — A handler returning NextResponse | NextResponse has an untyped second arm that accepts any body, so the return annotation checks nothing; the success payload must be annotated at its own declaration for the server shape and its client mirror to be held together | 7fbf8aa |
| 2026-08-09 | REGISTER | DR-138 added (accepted) — A Zod enum is added where a value crosses a trust boundary; for a column every call site writes as its own literal, the TypeScript union is the whole guard, and a paired validator is dead code that reads as protection | 7fbf8aa |
| 2026-08-09 | REGISTER | DR-139 added (accepted) — DR-123 covered task directives; this extends it to invariants, and adds the converse — pre-launch, the cost of preserving something wrong because it has consumers exceeds the cost of changing it, schema included | 855ea26 |
| 2026-08-09 | REGISTER | DR-140 added (accepted) — Stage-5 resolves before declaring rather than mutating declared rows, relationship endpoints derive from resolved mentions behind an admission gate, and the deterministic naming layer stops being the mechanism that decides two names are one thing | 855ea26 |
| 2026-08-09 | REGISTER | DR-141 added (accepted) — Concepts are generated per unit of knowledge with a residual grain guaranteeing coverage, not per key of a closed type vocabulary; the validator-enforced type taxonomy is withdrawn as a superset because it inverts what OKF is for | 855ea26 |
| 2026-08-10 | REGISTER | DR-142 added (accepted) — cocoindex leaves scripts/ for a singular root-level pipeline/ holding the whole runtime bundle plus its Python tests, package name unchanged; services/ is declined because DR-117’s moves-as-one-unit premise is false at the directory boundary, and deploy/ stays a root sib… | f3a2dcc |
| 2026-08-10 | REGISTER | DR-143 added (accepted) — The producer’s two pattern-matched source_documents reads gain a publication_status filter, matching every q_a_pairs read and TECH §2.1’s ratified corpus definition; widening the corpus to admit unpublished rows is rejected because it would oblige the residual grain to d… | 613f7f2 |
| 2026-08-10 | REGISTER | DR-144 added (accepted) — ruamel.yaml becomes a pinned producer dependency in id-428, overturning frontmatter.py’s contemporaneous no-pyyaml choice at the requirement level; PyYAML was never a candidate because safe_dump cannot meet id-440’s byte-faithful round-trip, and the migration must re-pro… | 613f7f2 |
| 2026-08-10 | REGISTER | DR-145 added (accepted) — source_documents.publication_status is ratified as a document-level REVIEW gate retained for clients who may want one, and admission_status becomes the home for withdrawing a document from retrieval; neither changes DR-025’s two gates, and R2’s queue-over-units-of-knowle… | b8eae3f |
| 2026-08-11 | REGISTER | DR-146 added (accepted) — The producer stops declaring bundle files as cocoindex target states and git_sync writes them instead, because the engine writes after the flow body returns and silently overwrites anything git_sync put on disk; write_bundle becomes pure content computation, and the engi… | ec87ea6 |
| 2026-08-11 | REGISTER | DR-147 added (accepted) — The entity_mentions surrogate id keys on the resolved canonical so identity and natural key agree, and the resolved canonical is a function of the accumulated decision record — pair cache, pins and prior canonicals seeded via is_existing_canonical — so re-runs cannot ren… | f1d15d6 |
| 2026-08-11 | REGISTER | DR-148 added (accepted) — Mentions from keep-and-watch and live-connected sources are engine-owned declarative rows; mentions from ingest-once sources cross a promotion boundary so the extracted knowledge outlives the source; external-referenced sources produce no mentions from bytes | f1d15d6 |
| 2026-08-12 | REGISTER | DR-149 added (accepted) — The closed 12-value entity_type vocabulary opens on the guided-open contract (prefer the twelve, mint only when nothing fits); type labels gain the DR-147 stability discipline — a re-run may add labels but never re-label an existing entity’s type, re-label attempts surfa… | c961b7f |
| 2026-08-12 | REGISTER | DR-150 added (accepted) — The effective LLM identity (resolved base URL + model) is a required argument of every memoized extractor so it participates in the memo key — a tier or model switch can never serve another identity’s memoized output; the signature change is the owner-approved one-time w… | cba35a2 |
| 2026-08-13 | SCHEMA | new migration 20260813100000_id434_entity_name_owner_kind_and_mention_wipe.sql — feat(id-434): resolution before declaration — the two-phase flow lands and the collision machinery dies (DR-140/DR-147/DR-148) | c744b11 |
