Discovery parity repair — integrated and verified
Canonical source and normal publication are complete:
| Owner | Implementation | Source work record |
|---|---|---|
| Reuse Surface | dd00b27 |
01af189 |
| NetKingdom | 49ddde4 |
3223039 normal identifier assignment |
| Railiance Bootstrap | 6927f5e |
8d23103 |
The native validator now refuses stale owner/index projections, duplicate IDs or paths and malformed index shapes without tracebacks. There are 23 new CLI regression cases, including null/list availability, malformed YAML/frontmatter and unvalidated index rows before Counter. Root independently passed all 30 parity/native-registry checks across 27 initial successes and three required filesystem-approved reruns. The sandbox write failures and initial isolated 238-test history below remain historical evidence.
Current local cohort validation is 0 errors, 0 warnings. Root forced fresh
hosted composition at 2026-10-16 19:25:11 UTC: all 70 reviewed IDs exactly
once, correct owners, no warning header, and both corrected owners' summary/tags
match their authoritative entries. See coordinator-hosted-refresh.json and
integration-r2.json for exact revisions and receipts. No further hosted readback
is needed for this bounded correction. Source publication does not establish
mandatory consumer fleet adoption or close every TSA-11 requirement.
Normal Reuse publication/consistency passed with existing warnings. Bootstrap
source and record publication succeeded, while its consistency result retains
11 historical failures and 36 warnings (zero automation errors). The unchanged
generated-only hook refused automatic brief-only commits; no bypass was used.
Public actions API requests returned HTTP404, so CI outcomes remain unverified.
The final combined NetKingdom projection sync against browser publication
015694ee414c802dc2ef1fa0120dfed610086e69 completed exit 0, zero failures or
automation errors, 29 existing/pre-repair warnings and five informational items.
It indexed browser T10/T11/T12 and retained their source IDs through the normal
tool; exact final receipt is netkingdom-parity-consistency-final.json.
NetKingdom's original brief staged blob/mode and worktree were preserved with
explicit staging isolation and race-checked restoration. Its current
WORK-RECORDS was preserved amid concurrent recovery/browser owner work.
TSA-12 still requires the selected rein/profile acceptance, actual schedule activation and the first unassisted scheduled fire. No production action, model spend, credential access or external message was performed.
Historical preparation and counterexamples
Prepared source candidate, 16 October 2026. No owner checkout or runtime changed.
The existing native reuse-surface validate --fail-on-warnings accepts index rows
whose names, summaries, owner, status, domain, tags, consumption modes or vector
no longer project their owner entry. It also accepts duplicate IDs/paths because
it converts paths to sets. This is a gap in the current tool, not a new observer
service. .forgejo/workflows/ci.yml:37 already runs this validator as a mandatory
job in Reuse Surface. Consumer fleet adoption is not claimed.
reuse-native-validator.patch extends that native command with parity and
uniqueness warnings. Strict mode rejects them; normal mode preserves the existing
warning policy. Equivalent vector whitespace remains accepted. It does not edit
owner entries, maturity assessments, credentials or hosted registrations.
Actual current source has 3 differing fields across 2 capabilities:
- NetKingdom bootstrap-recovery: summary.
- Railiance Bootstrap bootstrap-sequencing: summary and tags.
observed-drift.json retains exact entry/index values. Native CLI evidence shows
old exit 0, candidate exit 1, then exit 0 against corrected temporary indexes.
The two *-index-parity.patch files correct only those index fields to their
existing owner entries. No existing general index regeneration command was found;
these are constrained source projections, not newly authored capability claims.
Do not integrate the validator while silently ignoring its known cohort findings.
Review both owner patches in the same source integration wave. No generated-only
commit exception is implied; use the owners' normal publication workflow.
A separate synthetic duplicated row proves old exit 0 versus candidate exit 1. There is no observed duplicate in the actual reviewed cohort: 70/70 reviewed IDs appear exactly once across the current 60 local providers; those indexes contain 71 total entries including an additional out-of-denominator owner entry.
Tests: 11 new native CLI cases; the full isolated suite had 237 pass and one
missing-sibling-path failure. After resolving only the temporary federation
manifest's relative local paths against /home/worsch/reuse-surface, the single
failed composition test passed. All 238 tests have passed across those runs.
The failed first run remains in reuse-source.json. No manifest edit belongs to
the patch. Temporary reconstruction: /tmp/netkingdom-improvement-loop-next-reuse;
corrected owner registry copies: /tmp/netkingdom-improvement-loop-next-owners.
After review/integration, verification uses existing commands:
python3 -m pytest -q tests/test_index_parity.py tests/test_registry.py
reuse-surface validate --root /home/worsch/net-kingdom --fail-on-warnings
reuse-surface validate --root /home/worsch/railiance-bootstrap --fail-on-warnings
The existing Activity schedule remains disabled. ACTIVITY-WP-0047-T02 specifically
requires claiming-rein workstation checkout/hub acceptance, then owner release,
admin-sync and manual trigger; T03 requires the first unassisted scheduled fire.
The Oct15 rein candidate is rebuilt with startup proof but remains uninstalled
and unadmitted in its owner record, with real-model acceptance open. This is its
selected rein/profile dependency, not an invented dependency on completing the
unrelated task-scoped protected operation. Exact source hashes are retained in
schedule-dependency-evidence.json.
Kings Guard's cadence observer and Maturity Engine remain their existing owners;
a deterministic registry projection check creates neither posture nor a second
maturity assessor. The adopted coordination frame is 3600 seconds; source
configuration does not establish source/receiver runtime admission. The NetKingdom
knowledge pilot returned package 0.2.6, digest
8d1d6a9d4d07fec7b619618de7dfe2be2254c1790f85f4198c7fe19db9751c02,
withheld/orientation-only because sources changed. Current owner instructions,
companion and source artifacts were reviewed directly for this bounded change.
Next authority gates: coordinator and affected-owner source review, normal owner publication and CI, then native hosted source refresh/readback if publication is admitted. TSA-11 remains open for full hosted accuracy/version/link requirements; TSA-12 remains open for accepted runtime activation, unassisted firing, checkpoint and changed-state delivery, owner remediation and native remeasurement. No production action, model spend, credential access or external message occurred.