KB-5EC5

F-5 Ownership-Seed Rollback-Only — 03 Direct & Inherited Owner Results

2 min read Revision 1
one-roofphase1f5resultsdirectinherited2026-06-02

03 — Direct & Inherited Owner Results

Executed in BEGIN..ROLLBACK via psql -f over ssh. Both seed inserts returned INSERT 0 1; own_in_txn=2. Children of GRP-WORKFLOW (live): workflows, workflow_steps.

Direct owner — VERIFIED

(agents, audit) → owner GOV-COUNCIL, resolution=direct, depth=0, source_anchor=(collection, agents). Direct accountability resolves at depth 0 regardless of is_inherited_anchor.

Inherited owner — VERIFIED

Group anchor (group, GRP-WORKFLOW, policy, is_inherited_anchor=true) fans out to both children at scope policy: (workflows, policy) and (workflow_steps, policy) → owner GOV-DOT, resolution=inherited, depth=1, source_anchor=(group, GRP-WORKFLOW). Proven over real collection_registry."group" containment committed in F-4.

Missing owner — VERIFIED

(agents, policy) remains gap → agents_policy_gap=1.

Effective-owner accounting

direct=2, inherited=2. Why direct=2 not 1: the group node GRP-WORKFLOW is itself a node (appears as parent_ref); its own anchor resolves it as direct owner of itself at depth 0. Harmless — the group node is NOT in v_governance_object_inventory, so contributes 0 gap rows. Inventory-scoped coverage = 1 direct (agents/audit) + 2 inherited = 3 (see doc 04).

Back to Knowledge Hub knowledge/dev/reports/architecture/one-roof-phase1-coverage-dry-run-f5-ownership-seed-rollback-only-2026-06-02/03-direct-and-inherited-owner-results.md