// SPDX-License-Identifier: CC-BY-SA-4.0
= Known Tensions Register

Status values used here are: `contradiction`, `architectural tension`, `implementation debt`, `terminology drift`, `capacity limitation`, and `known incomplete work`.

[cols="2,1,1,3,3,1",options="header"]
|===
|Tension |Class |Priority |Current containment |Smallest useful next action |Evidence
|Agent healing vs contestable authority |architectural tension |high |Bound agent scope; require review and challenge records |Define a capability and appeal profile |designed
|Formal disposition vs faithful representation |architectural tension |high |Require lowering assumptions and affected-context review |Specify faithful-lowering evidence fields |designed
|MAA reversibility vs irreversible external effects |architectural tension |high |Ban generic rollback claims; declare state boundary |Review integration profile against canonical MAA |designed
|Provenance vs privacy, redaction, and secret destruction |architectural tension |high |Permit accountable redaction without false continuity |Define redaction and secret-destruction receipts |designed
|Open-source identity vs enforceable ethical-use restrictions |contradiction |high |Do not claim both for the same licensed grant |Obtain licence-policy/legal review |assumed
|Open contribution vs founder-only authorship checks |architectural tension |high |Separate perimeter authority from provenance/IP |Publish reviewable contributor criteria |designed
|Machine-readable governance vs human contestability |architectural tension |high |Require faithful human view and challenge route |Add validator checks for declared appeal route |designed
|Type abstraction vs trope particularity |architectural tension |medium |Record material particulars lost in abstraction |Develop a faithful-representation profile |known incomplete work
|Mirroring vs containment and revocation |architectural tension |high |Treat mirrors as external effects; document quarantine |Inventory forge propagation and revocation limits |assumed
|Trustfile concern creep |implementation debt |high |Separate full standard, profile, projection, enforcement |Reconcile Trust artifacts after source-pack review |known incomplete work
|ALARP vs absolute `MUST` claims |terminology drift |high |Require exception or contradiction record |Add normative-language guidance |designed
|Minimal trusted bases vs estate-wide capability accretion |architectural tension |high |Require scoped capabilities and dependency evidence |Inventory trusted-base growth |assumed
|===

Entries remain open until an authorised decision records resolution or accepted containment. A validator passing does not close a tension.
