# Replace canonical terminology in records

status: resolved
ticket_id: 5277a082-e6d0-40aa-97a9-3a6e43fb300c
created_at: 2026-05-03T21:15:58.971585485+00:00
updated_at: 2026-05-03T21:55:07.066976989+00:00
priority: P2
ticket_type: chore
labels: docs, requirements, glossary
resolved_at: 2026-05-03T21:55:07.066976989+00:00
resolution: accepted

## Body

Update source records under ./records so Benac-authored requirements and glossary records avoid using canonical as a Benac concept, replacing it with precise mechanism wording and adding the requested boundary/capability/secret requirements where appropriate.

## Proposed resolution

Updated ./records to avoid canonical as Benac terminology: retired six standalone canonical term records, added a Canonical avoid-term record, rewrote affected glossary and requirement records to use explicit DRISL/CID/signature/payload wording, added BENAC-HOST-003, BENAC-CAP-006, and BENAC-SEC-006, refreshed generated docs, and verified with npm test.

## History

### 1. caller - created - 2026-05-03T21:15:58.971585485+00:00
status_after: pending

Ticket created: Replace canonical terminology in records

### 2. handler - handler_picked_up - 2026-05-03T21:16:15.020560807+00:00
status_after: in_progress

Phase 0 complete: confirmed the operator MCP tool list and fetched ticket context. Starting Phase 1: inventory records containing canonical terminology.

### 3. handler - comment - 2026-05-03T21:17:17.332806882+00:00

Phase 1 complete: inventoried canonical/canonicalization usage under ./records. Found usage in 25 requirement records and 42 term records, including six standalone canonical term records to retire and one avoid-term record to add. Starting Phase 2: glossary source-record edits.

### 4. handler - comment - 2026-05-03T21:22:18.693514105+00:00

Phase 2 complete: retired the six standalone canonical term records, added a Canonical avoid-term record, and rewrote remaining glossary records to name DRISL bytes, required CID form, signature/CID payloads, host-only metadata, and normalized/validated output. Starting Phase 3: requirement source-record edits and new requirements.

### 5. handler - comment - 2026-05-03T21:26:12.640157690+00:00

Phase 3 complete: rewrote requirement records to name DRISL bytes, DRISL-encoded objects, required CID string form, structured document CIDs, signed payloads, and host-only metadata. Added BENAC-HOST-003, BENAC-CAP-006, and BENAC-SEC-006. The only remaining canonical text under records is the Canonical avoid-term record itself. Starting Phase 4: rebuild generated docs and validate the dataset.

### 6. handler - resolution_proposed - 2026-05-03T21:27:36.525463317+00:00
status_after: proposed_resolution

Phase 4 complete: rebuilt the generated glossary and SyRS and ran npm test successfully. A docs/records grep now shows canonical only in the new Canonical avoid-term record and its generated glossary entry. Proposing resolution.

### 7. handler - comment - 2026-05-03T21:30:49.911840972+00:00

Post-resolution publish/deploy phase starting: previous phase reached proposed_resolution with npm test passing and generated docs rebuilt. Next step is scoped git stage/commit/push, followed by production deploy.

### 8. handler - comment - 2026-05-03T21:32:11.522213873+00:00

Publish phase complete: committed docs: avoid canonical terminology as a1ef245 and pushed feat/dasl-cid-drisl to gitlab. Starting deploy phase with scripts/deploy.sh.

### 9. handler - comment - 2026-05-03T21:33:16.596560319+00:00

Deploy phase complete: scripts/deploy.sh completed successfully for build a1ef2453b2ebcc825cd3e3533e669e7b8f97c25c. Production probes all returned 200 and the public PWA index matched local bundle benac-pwa-4d18cfb2a790135b.js.

### 10. human - resolution_accepted - 2026-05-03T21:55:07.066976989+00:00
status_after: resolved

Caller accepted the proposed resolution.

Replace canonical terminology in records

resolved 5277a082-e6d0-40aa-97a9-3a6e43fb300c

created_at: 2026-05-03
updated_at: 2026-05-03
priority: P2
ticket_type: chore
labels: docs, requirements, glossary
resolved_at: 2026-05-03
resolution: accepted

Body

Update source records under ./records so Benac-authored requirements and glossary records avoid using canonical as a Benac concept, replacing it with precise mechanism wording and adding the requested boundary/capability/secret requirements where appropriate.

Update source records under ./records so Benac-authored requirements and glossary records avoid using canonical as a Benac concept, replacing it with precise mechanism wording and adding the requested boundary/capability/secret requirements where appropriate.

Proposed resolution

Updated ./records to avoid canonical as Benac terminology: retired six standalone canonical term records, added a Canonical avoid-term record, rewrote affected glossary and requirement records to use explicit DRISL/CID/signature/payload wording, added BENAC-HOST-003, BENAC-CAP-006, and BENAC-SEC-006, refreshed generated docs, and verified with npm test.

Updated ./records to avoid canonical as Benac terminology: retired six standalone canonical term records, added a Canonical avoid-term record, rewrote affected glossary and requirement records to use explicit DRISL/CID/signature/payload wording, added BENAC-HOST-003, BENAC-CAP-006, and BENAC-SEC-006, refreshed generated docs, and verified with npm test.

History (10 events)

caller · created · 2026-05-03T21:15:58.971585485+00:00 (2026-05-03) → pending
Ticket created: Replace canonical terminology in records
handler · handler_picked_up · 2026-05-03T21:16:15.020560807+00:00 (2026-05-03) → in_progress
Phase 0 complete: confirmed the operator MCP tool list and fetched ticket context. Starting Phase 1: inventory records containing canonical terminology.
handler · comment · 2026-05-03T21:17:17.332806882+00:00 (2026-05-03)
Phase 1 complete: inventoried canonical/canonicalization usage under ./records. Found usage in 25 requirement records and 42 term records, including six standalone canonical term records to retire and one avoid-term record to add. Starting Phase 2: glossary source-record edits.
handler · comment · 2026-05-03T21:22:18.693514105+00:00 (2026-05-03)
Phase 2 complete: retired the six standalone canonical term records, added a Canonical avoid-term record, and rewrote remaining glossary records to name DRISL bytes, required CID form, signature/CID payloads, host-only metadata, and normalized/validated output. Starting Phase 3: requirement source-record edits and new requirements.
handler · comment · 2026-05-03T21:26:12.640157690+00:00 (2026-05-03)
Phase 3 complete: rewrote requirement records to name DRISL bytes, DRISL-encoded objects, required CID string form, structured document CIDs, signed payloads, and host-only metadata. Added BENAC-HOST-003, BENAC-CAP-006, and BENAC-SEC-006. The only remaining canonical text under records is the Canonical avoid-term record itself. Starting Phase 4: rebuild generated docs and validate the dataset.
handler · resolution_proposed · 2026-05-03T21:27:36.525463317+00:00 (2026-05-03) → proposed_resolution
Phase 4 complete: rebuilt the generated glossary and SyRS and ran npm test successfully. A docs/records grep now shows canonical only in the new Canonical avoid-term record and its generated glossary entry. Proposing resolution.
handler · comment · 2026-05-03T21:30:49.911840972+00:00 (2026-05-03)
Post-resolution publish/deploy phase starting: previous phase reached proposed_resolution with npm test passing and generated docs rebuilt. Next step is scoped git stage/commit/push, followed by production deploy.
handler · comment · 2026-05-03T21:32:11.522213873+00:00 (2026-05-03)
Publish phase complete: committed docs: avoid canonical terminology as a1ef245 and pushed feat/dasl-cid-drisl to gitlab. Starting deploy phase with scripts/deploy.sh.
handler · comment · 2026-05-03T21:33:16.596560319+00:00 (2026-05-03)
Deploy phase complete: scripts/deploy.sh completed successfully for build a1ef2453b2ebcc825cd3e3533e669e7b8f97c25c. Production probes all returned 200 and the public PWA index matched local bundle benac-pwa-4d18cfb2a790135b.js.
human · resolution_accepted · 2026-05-03T21:55:07.066976989+00:00 (2026-05-03) → resolved
Caller accepted the proposed resolution.

← all tickets · home