#534 D: Fact owners on the models #540
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#540
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
Child of #534 (ADR-0169). Parent design points and comments on #534. Lands after #535.
Tasks
Pseudo-Ruby:
Acceptance criteria
Blocking edges
Blocked by: #535 and #539
Origin
Work started via /os-sdlc:implement on branch ticket-540 (session d233a2f7-977a-419d-99ea-011b6e1e66f8).
Pipeline implementation 2 (dispatches 16-26) returned implementation_complete after one increment: StepResult#summary only (commit on ticket-540). behavior-verifier passed with six of seven tasks untouched, a wrong completion verdict. Not closing. Opening a new implementation on the same branch for the remaining tasks.
Resolution
Done: Fact owners live on the models: StepResult#summary, Dispatch#step_summaries, StepResult.lint_failures_for(implementation), Handoff.latest(implementation, from:), LintOffenseLine (replaces BriefFacts::LintFailureRow), TestDiff(project, root:)#to_s, Implementation#latest_dispatch. BriefFacts asks them and no longer builds joins or duplicates the verdict rule. Every moved behavior keeps its BriefFacts expectations and every new model method has a direct test.
Evidence: Branch ticket-540, seven per-increment commits
acc1862,cf32bb2,3e52065,68f1036,120095e,789bbaa,f3e9232plus history row10a055a, merged to main 2026-09-09. Suite 1109 runs green. Pipeline: implementation 2 (dispatches 16-26) declared complete after one task, rejected; implementation 3 (dispatches 27-86) landed the rest and escalated on dispatch_cap:60 at the last suite-check with the suite green; the final five-line increment (Implementation#latest_dispatch wrapper, BriefFacts#gate_results asks the aggregate) was reviewed by the orchestrator instead of contract-auditor and behavior-verifier. Two flake reruns (autocorrect prepass whitespace race, getcwd hook race). Escalation capture: see step 1 result.Follow-ups: #541 and #542 next in the #534 chain; escalation cause captured per step 1 (ticket number or #540 comment)