ARCH-01 — Principal equivalence classes, conflict detection, and serialized merges #824
Open
opened 2026-07-22 19:42:25 -05:00 by jcwalker3
·
0 comments
No Branch/Tag Specified
master
fix/issue-842-conflict-fix-lease-lifecycle
fix/issue-843-cross-role-allocation-handoff
fix/issue-790-slice-a-heartbeat-policy
feat/issue-628-autonomous-handoffs-orchestration
feat/issue-634-readonly-system-health-api
feat/issue-638-webui-app-shell-phase1
fix/issue-840-cross-role-queue-allocation
feat/issue-822-atomic-install-authority-kernel
feat/issue-633-console-authz-audit-model
feat/issue-636-inventory-api
fix/issue-815-preflight-worktree-forwarding
feat/issue-812-publish-unpublished-commit
feat/issue-635-project-registry-api
feat/issue-798-worker-registry-schema
feat/issue-610-live-remote-parity
docs/issue-632-web-console-architecture
fix/issue-760-exact-owner-renewal
fix/issue-787-kill-segment-separators
chore/issue-681-preserve-review-session-wip
v1.1.0
Labels
Clear labels
allocator
anti-stomp
architecture
bug
chore
codex
concurrency
contamination
control-plane
dashboard
database
design
documentation
enhancement
gitea
glitchtip
important
incident
incident-bridge
integration
jenkins
labels
leases
mcp
mcp-health
mcp-menu
multi-project
mutating
nice-to-have
observability
portability
preflight
protected-branch
queue
read-only
reconnect
recovery
refactor
release
reliability
resumable-review
reviewer
roadmap
safety
security
self-hosted
sentry
stale-runtime
status:blocked
status:in-progress
status:pr-open
status:ready
terminal-lock
testing
tracker
type:bug
type:feature
type:feature
type:guardrail
visibility
workflow
workflow-hardening
workflow-hardening
Controller-owned work allocator
Prevent concurrent LLM session stomping
Architecture / structural design
OpenAI Codex client / workflow session surface
Concurrent session safety
Workflow or session contamination incident
MCP control-plane coordination and allocation authority
MCP operational dashboard/queue view
Internal coordination storage (SQLite/Postgres)
Design / investigation, no implementation
Docs / runbooks
New feature or improvement
Gitea MCP workflow
GlitchTip integration
Operational or process incident requiring durable audit trail
Sentry-to-Gitea incident bridging
Integration testing
Jenkins integration
Label taxonomy management
Lease adopt/release/expire lifecycle
MCP server / tooling
MCP namespace and runtime health
MCP menu surface
Work spanning multiple monitoring projects or Gitea repos
Mutating action; requires gating
Observability, metrics, traces, error reporting
Cross-platform / portability
Shared preflight gates before mutation
Protected branch / stable-branch policy concern
Work queue visibility and allocation
Read-only, no mutation
MCP client reconnect/reload recovery path
Recovery paths for stale/foreign leases
Code refactor / restructure
Release / versioning
Reliability / failure handling
Persist and resume prepared review verdicts across sessions
Reviewer workflow tooling
Roadmap / umbrella issue
Safety rails and fail-closed mutation guards
Security / trust boundary
Self-hosted infrastructure integration
Sentry error monitoring integration
Stale backend daemon / runtime-vs-master parity failures
Issue is blocked
Issue is being worked on
Issue has an open pull request
Issue is ready for work
Terminal review lock (#332) path
Tests / test coverage
Issue tracker hygiene / meta
Bug or defect
Feature or enhancement
Feature or enhancement
Safety gate or guardrail
Workflow state visibility for LLMs/operators
Cross-tool workflow
LLM workflow coordination hardening
LLM workflow coordination hardening
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Scaled-Tech-Consulting/Gitea-Tools#824
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Candidate architecture requiring executable validation; not yet approved, production-ready, or certified.
Parents: #820, #821. Depends on: #822 (class root +
current_class_id).1. Summary / objective
Implement principal equivalence: one current class per principal, append-only merge/linkage history, a full cross-class conflict scan before any merge, serialized merges, and permanent
same_principaldecisions.2. Security/correctness problem
Equivalence decides whether two transport identities are "the same actor" for separation-of-duties. A wrong or racing merge collapses distinct actors (defeating SoD) or contradicts a prior distinctness proof.
3. Threat model / failure modes
Same-issuer ids merged as one; a merge that ignores a distinct decision between non-named members of the two classes; concurrent crossing merges; direct
current_class_idrewrite; superseding a permanent same-decision; cyclic/redirectedsuperseded_by.4. In-scope behavior
principals.current_class_idNOT NULL FK (one current class).[SCHEMA].principal_linkages(principal_a<principal_b, disposition∈{same,distinct}, evidence_id, status∈{active,superseded}, supersedes),UNIQUE(a,b) WHERE status='active'; unlimited immutable historical rows.[SCHEMA].same_principalforbidden; cross-transport / transport↔operator_key / cross-key permitted with the matching evidencereference_kind.[SCHEMA]trigger.merge_equivalence(merge mode only): resolve classes; equal→no-op; full transitive scan of every activedistinct_principalacross the two complete member sets →EQUIVALENCE_CONTRADICTIONon any hit; canonical survivor = lowerclass_id; rewrite absorbed members'current_class_id(permitted only in merge mode); set absorbed classsuperseded_by; insertsame_principalactive.principal_immutableexemptscurrent_class_idonly in merge mode).[SCHEMA].same_principalpermanent (no_supersede_same); onlydistinct_principalmay be superseded, same canonical pair, one transaction.class_supersede_acyclic.[SCHEMA].5. Exclusions
No cross-repository identity, no evidence-record creation (consumes existing valid records), no UI.
6. Schema/operation contracts
principal_equivalence_classes,principal_class_members(orcurrent_class_idon principals — implement whichever the executable design proves cleaner; the NOT NULL single-value guarantee is required),principal_linkages. Operations:merge_equivalence,record_distinct_principal.7. SQLite behavior
BEGIN IMMEDIATE; survivor = lower id; the transitive scan reads both complete member sets before writing.8. PostgreSQL behavior
SERIALIZABLE;SELECT … FOR UPDATEon both class rows in deterministic id order; retry on serialization failure; concurrent crossing merges cannot both commit.9. Concurrency / transaction requirements
Deterministic lock order prevents deadlock; two concurrent merges touching overlapping classes serialize; a merge contradicted by an existing distinct decision is rejected, not silently overridden.
10. Structured results
MERGED,MERGE_NOOP,EQUIVALENCE_CONTRADICTION,LINKAGE_ISSUER_FORBIDDEN,SUPERSEDE_SAME_FORBIDDEN,SERIALIZATION_RETRY,AUTHORIZATION_DENIED.11. Enforcement classification
NOT NULL class, active-linkage uniqueness, issuer rule, acyclic supersede, no-supersede-same
[SCHEMA]; digest of evidence subject[TRUSTED-SERVICE](from the evidence issue); merge serialization[TRUSTED-SERVICE]/backend locks.12. Acceptance criteria
same_principal.same_principalinserted only viamerge_equivalence.same_principaldecisions permanent; only distinct superseded (same pair, one txn).current_class_idnot directly editable (except merge mode).superseded_byacyclic, no redirect.13. Named tests
t_one_class(+),t_same_issuer_same(−),t_cross_issuer_wrong_proof(−),t_direct_same_insert(−/raw-bypass),t_merge_transitive_conflict(−),t_supersede_same(−),t_direct_class_edit(raw-bypass),t_concurrent_crossing_merge(concurrency, both backends),t_supersede_cycle(−).14. Audit events / evidence
equivalence_merged,equivalence_contradiction,distinct_recorded,linkage_superseded. Test-run output is evidence.15. Dependencies / parent
Parents #820, #821; depends on #822; consumes evidence records from the typed-evidence issue (linkage proofs).
16. Definition of done
Executable on SQLite and PostgreSQL; ACs pass incl. concurrency + raw-bypass; bounded PR; no self-review/merge.
17. Known limitations / deferred
Class splitting is unsupported (merges permanent). Reversing a wrong same-decision requires operator-level re-provisioning of the principals — out of scope; note as a follow-up if needed.