Rights Freedoms Obligation Mapping

Map every asserted right or freedom to its bearer, counterpart relation, scope, justification, conflict, and remedy before deciding what must be protected, provided, permitted, restrained, or reviewed.

Version

v1 · 2026-08-24 · History

Solution archetype #

899

Problem family

Authority, Accountability, Legitimacy & Fair-Process Failure

Problem subfamily

Rules, Rights, Obligations & Consistency

Essence

Rights–Freedoms Obligation Mapping turns compressed normative language into a usable relationship architecture. The key move is not to rank “rights” against “freedoms” as abstract nouns. It is to ask what kind of position each statement creates, for whom, against whom, concerning what action or object, within which scope, under which authority, and with what consequence if the relation is breached.

The method recognizes that several different structures are routinely called a right. A claim places a duty on another party. A liberty means the bearer has no duty not to act, paired with another party's lack of a claim to prevent that act. A power allows one actor to alter a normative relation, paired with another actor's liability to that change. An immunity protects a bearer from someone else's power, paired with that actor's disability. These categories can coexist in one policy. For example, a user may have a liberty to publish, a claim that the operator follow a published moderation procedure, a power to withdraw consent for some data uses, and an immunity from retroactive alteration of a protected contractual term.

The archetype adds operational depth to that classification. It identifies positive provision and negative restraint duties, defines scope and exceptions, traces the source and legitimacy of authority, maps conflicts, tests restrictions, translates the result into implementation, and attaches remedy and review. Its output is not a mathematically final answer to moral conflict. It is a transparent, contestable account of what each proposed answer would require.

Compression statement

“Right” can mean a protected liberty to act, a claim that another actor must act or refrain, a power to alter legal or organizational relations, or an immunity from another actor's power. These positions have different counterpart structures and implementation costs. Rights–Freedoms Obligation Mapping prevents category drift by classifying each asserted position; naming bearer and counterparty; specifying object, jurisdiction, conditions, duration, and exceptions; tracing positive provision and negative restraint duties; detecting collisions; testing authority, necessity, proportionality, and least-restrictive alternatives; and attaching enforcement, remedy, change, and review paths. It produces a contestable relationship map rather than pretending substantive conflicts can be solved by a single slogan or scalar balance.

Canonical formula: asserted_interest + bearer_and_counterparty_map + normative_relation_classifier + scope_and_condition_boundary + counterpart_obligation_map + conflict_matrix + authority_and_warrant_record + proportionality_and_least_restrictive_test + remedy_and_change_path -> coherent_contestable_rights_freedoms_architecture

When This Archetype Applies

No catalog groundingNone of the structural conditions is currently represented by an accepted prime or domain-specific abstraction.

Diagnostic problem

A policy, contract, platform rule, organizational mandate, or public controversy uses “right,” “freedom,” “permission,” “entitlement,” “choice,” and “duty” as if they were interchangeable. The statement omits the relation's bearer, counterparty, object, jurisdiction, conditions, costs, exceptions, or remedy. Competing actors then debate abstractions while implementing incompatible assumptions: a liberty is treated as a guaranteed service, a claim is treated as optional permission, a power is mistaken for a liberty, or one party's protected zone silently creates an unassigned duty or burden for another.

What this problem means

Ambiguous rights language compresses a relational system into a prestigious label. Compression is often politically and communicatively useful, but it becomes dangerous when the implementation boundary arrives. A product manager hears “right to access” and creates a permission. An operations team hears the same phrase and assumes a service-level obligation. A finance team sees no assigned capacity owner. A security team adds a revocation power. A customer expects a remedy. Each interpretation may be coherent alone, yet the combined system is contradictory.

The structural defect is deeper than unclear wording. Normative positions are relational: they distribute freedom, obligation, exposure, authority, protection, cost, and remedy among actors. Omitting one side does not remove it; it makes the distribution informal. Informal distributions usually favor parties with implementation control, information, money, status, or access to review.

The same defect appears in substantive conflict. “Balance privacy and safety” is not yet a decision frame. Which privacy claim or liberty, held by whom, against which collection or disclosure? Which safety claim, owed by whom, supported by what evidence and capacity? Who has power to change the rule? Which actors are liable to that change? What immunity or non-waivable floor limits the power? What remedy exists after error? Without these questions, balancing becomes an intuitive comparison of slogans, and the party who defines the metrics controls the result.

The archetype also addresses implementation decay. Rights and freedoms change through policy versions, technical releases, emergency rules, service closures, jurisdiction changes, reorganizations, and accumulated exceptions. A stable map needs change, transition, and reliance rules so the operational relation cannot drift while public language remains constant.

Applicability expression9 distinct conditions

Right lacks counterpartandProvision-interference conflationandColliding rights claimsandPermissions encode entitlementsandUnjustified public-interest restrictionandUnclear power reviewandLiberty lacks enabling capabilityandClaim lacks duty bearerandExceptions hollow right

Algebraic1∧2∧3∧4∧5∧6∧7∧8∧9

groundedpartly groundedopen

9 conditions, all required.

9Required in every casenumbered 1–9

These hold no matter which pattern applies.

1

Right lacks counterpart · open

A proposal claims to protect a right or freedom without identifying the counterpart relation. more

and — also required

2

Provision-interference conflation · open

Positive provision and negative noninterference obligations are being conflated. more

and — also required

3

Colliding rights claims · open

Multiple rights claims collide across people, roles, resources, jurisdictions, or time. more

and — also required

4

Permissions encode entitlements · open

A permission system is expected to encode substantive entitlements or immunities. more

and — also required

5

Unjustified public-interest restriction · open

A restriction is justified by broad public interest without necessity or least-restrictive analysis. more

and — also required

6

Unclear power review · open

An actor has formal power to change another's position, but the scope or review path is unclear. more

and — also required

7

Liberty lacks enabling capability · open

A protected liberty is unusable because capability, access, or institutional provision is absent. more

and — also required

8

Claim lacks duty bearer · open

A claim is recognized rhetorically but has no duty bearer, capacity allocation, enforcement, or remedy. more

and — also required

9

Exceptions hollow right · open

Exceptions accumulate until the nominal right or freedom has no stable operational core. more

Other requirements and context (1)

Why these sit outside the expression

Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.

• Supporting contextA dispute process exists but the underlying normative positions remain unclassified. more

Coverage

0 of 9 conditions grounded · 9 open.

Read the methodology · Download the trigger-logic data

When to Use This Archetype

Use this archetype when a system must translate normative language into action and the words “right,” “freedom,” “permission,” “entitlement,” “choice,” “power,” or “duty” are carrying more than one meaning. It is particularly useful before writing policy, negotiating a contract, encoding permissions, delegating authority, designing a consent flow, limiting conduct, rationing a service, or sending a contested issue into adjudication.

The strongest signal is a missing counterparty. If someone says a person “has a right,” ask who must act, refrain, provide, recognize, enforce, or accept review. If no answer exists, the statement may name a liberty, aspiration, interest, or unfinished claim rather than an operational claim-right. Conversely, when someone says an actor is “free” to do something, ask whether the action changes another party's position, consumes shared capacity, enters a protected domain, or depends on a provision duty. The apparent liberty may include a power, constraint, or claim that needs separate treatment.

Use the archetype early enough to shape the decision, not merely as documentation after implementation. It is most valuable when multiple teams or jurisdictions would otherwise encode different interpretations. It is also useful during review: repeated appeals, access failures, inconsistent enforcement, and exception growth often reveal that the original relation was never typed or scoped precisely.

Do not use it to simulate legal authority. A mapping team can expose assumptions, omissions, and implementation consequences, but legitimate institutions and qualified reviewers must decide jurisdiction-specific doctrine, public authority, collective rights, non-waivable protections, and contested priorities.

Structural Problem

Ambiguous rights language compresses a relational system into a prestigious label. Compression is often politically and communicatively useful, but it becomes dangerous when the implementation boundary arrives. A product manager hears “right to access” and creates a permission. An operations team hears the same phrase and assumes a service-level obligation. A finance team sees no assigned capacity owner. A security team adds a revocation power. A customer expects a remedy. Each interpretation may be coherent alone, yet the combined system is contradictory.

The structural defect is deeper than unclear wording. Normative positions are relational: they distribute freedom, obligation, exposure, authority, protection, cost, and remedy among actors. Omitting one side does not remove it; it makes the distribution informal. Informal distributions usually favor parties with implementation control, information, money, status, or access to review.

The same defect appears in substantive conflict. “Balance privacy and safety” is not yet a decision frame. Which privacy claim or liberty, held by whom, against which collection or disclosure? Which safety claim, owed by whom, supported by what evidence and capacity? Who has power to change the rule? Which actors are liable to that change? What immunity or non-waivable floor limits the power? What remedy exists after error? Without these questions, balancing becomes an intuitive comparison of slogans, and the party who defines the metrics controls the result.

The archetype also addresses implementation decay. Rights and freedoms change through policy versions, technical releases, emergency rules, service closures, jurisdiction changes, reorganizations, and accumulated exceptions. A stable map needs change, transition, and reliance rules so the operational relation cannot drift while public language remains constant.

Intervention Logic

Begin with the concrete interest or action rather than the label. Describe what a person or institution seeks to do, receive, avoid, change, protect, or contest. Identify all directly and indirectly affected actors. Then classify each relation. The classifier is a gate: ambiguous mixed positions are decomposed, and classification is revisited when implementation reveals a missing counterparty or unexpected burden.

Next, map correlatives and opposites. A claim should reveal a duty bearer. A liberty should reveal the relevant no-claim and noninterference zone. A power should reveal who is liable to a change. An immunity should reveal whose power is disabled. This relational map is then scoped by object, role, jurisdiction, context, time, conditions, exceptions, and termination. Positive obligations are separated from negative restraints so provision capacity and noninterference are not silently exchanged.

Only after classification and scope should the team map conflicts. Some conflicts disappear when positions are narrowed; others become resource, timing, jurisdiction, or remedy problems rather than absolute contradictions. Remaining constraints are tested against authority, evidence, purpose, necessity, proportionality, and less restrictive alternatives. The analysis retains distribution and dissent instead of forcing all positions into a single score.

Finally, translate the adopted map into operational rules and remedies. Policy prose, permissions, service commitments, audit signals, review authority, restoration, compensation, and change rules should trace back to the same relation record. Representative scenarios test ordinary and edge cases. Versioned reviews catch changes in authority, technology, capacity, evidence, or affected populations.

Key Components

The first four components define the relation. The Affected Interest and Bearer Map establishes whose interests are visible. The Normative Relation Classifier supplies the typed grammar. The Counterpart Obligation Map assigns restraint, provision, enforcement, or exposure to specific actors. The Liberty and Noninterference Zone protects open action space without pretending that permission automatically creates resources or immunity.

The next three components establish boundaries and legitimacy. Scope, Condition, and Jurisdiction Boundary prevents universal language from hiding contextual limits. Normative Conflict and Interaction Matrix identifies contradictions, cumulative burdens, scarce capacity, and indirect effects. Authority Source and Warrant Record separates the fact that an actor can impose a rule from the claim that the actor may legitimately do so.

Constraint Justification Test and Proportionality and Least-Restrictive Screen form the scrutiny layer. The former asks whether a restriction has legitimate purpose, evidence, harm definition, and authority. The latter compares burdens and alternatives after the positions are clear. These should not be collapsed: a proportionate measure can still lack authority, and an authorized measure can still be unnecessarily broad.

Remedy, Enforcement, and Review Path makes the structure credible. Change, Revocation, and Transition Rule protects against silent erosion and handles reliance. Normative Relation Decision Record maintains end-to-end traceability.

Optional components deepen contexts where formal liberty and effective capability diverge, where collective and individual positions interact, or where reasonable disagreement remains unresolved. They are optional because not every mapping exercise requires resource modeling, collective overlays, or a formal dissent register; they are not optional when those conditions materially determine exercise or burden.

Common Mechanisms

The Hohfeldian Relation Matrix is the most recognizable analytic mechanism. It is valuable because it forces actor-pair and correlative reasoning, but it is not the archetype. A matrix can classify relations while omitting capacity, scope, conflicts, justification, remedies, and change.

The Claim–Liberty Classification Tree is a faster intake mechanism. It asks whether another party must act, refrain, accept a status change, or lack power. It is useful for policy workshops and requirements reviews, where ambiguous phrases need to be decomposed before detailed mapping.

The Counterparty Obligation Register translates claims into accountable ownership, service levels, enforcement, and capacity. Rights-Conflict Scenario Table then tests combinations of actors, conditions, scarce resources, and exceptions. The Least-Restrictive Alternative Screen and Proportionality Balancing Record support reasoned constraint selection without hiding evidence or dissent.

The Permission–Entitlement Crosswalk is essential in digital and organizational implementation. It catches situations where a user can technically act without having a service claim, or has a policy claim that the software cannot execute. Remedy Traceability Review follows a breach from detection through notice, review authority, state change, restoration, and closure. It detects “appeals” that can explain a result but cannot correct it.

Mechanisms should be selected according to the problem. A simple role-policy clarification may need the classification tree, relation matrix, and decision record. A high-stakes public restriction may require the full scenario, alternatives, proportionality, dissent, remedy, and independent review set.

8 documented mechanisms across 4 implementation forms.

The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.

Analysis, Modeling & Optimization · 2 mechanisms

• Hohfeldian Relation Matrix — Lays every asserted position into a grid of its jural correlative and opposite, so a claim with no matching duty cell — or a liberty mistaken for a claim — becomes visible at a glance.
• Rights-Conflict Scenario Table — Runs concrete combinations of actors, conditions, and scarce resources to reveal which rights collisions are real and which dissolve once scope is fixed.

Assessment, Review & Assurance · 3 mechanisms

• Least-Restrictive Alternative Screen — Requires reviewers to consider whether a less restrictive but still effective response would achieve the same purpose.
• Permission–Entitlement Crosswalk — Maps technical permissions against substantive entitlements to catch capabilities with no claim behind them and claims the system cannot actually execute.
• Remedy Traceability Review — Follows a breach from detection through notice, review, state-change, and restoration to confirm the remedy can actually change the outcome — not just explain it.

Decision, Gate & Allocation · 1 mechanism

• Claim–Liberty Classification Tree — Routes each ambiguous 'right' phrase through ordered yes/no questions to a single position type — claim, liberty, power, or immunity — before any detailed mapping begins.

Record, Log & Register · 2 mechanisms

• Counterparty Obligation Register — Turns each recognized claim into a line item with a named duty-owner, a service level, the capacity behind it, and an enforcement hook — so no obligation floats unassigned.
• Proportionality Balancing Record — Records the reasoned weighing of a constraint's burden against its justified purpose, preserving the evidence, the value judgments, and the dissent behind the call.

Parameter / Tuning Dimensions

Granularity is the first tuning choice. Principle-level maps communicate stable commitments; actor-pair maps expose implementation. Mature practice keeps both: a concise public layer with traceable detailed relations underneath. Excess detail without hierarchy becomes unmaintainable, while broad language without counterparties becomes performative.

Scope precision should increase with severity and diversity of context. High precision names jurisdiction, role, object, trigger, duration, exception, and termination. Yet brittle precision can create loopholes and exclude unanticipated cases. Scenario testing and review triggers balance that tradeoff.

Positive-obligation depth depends on practical exercise. Some liberties need only noninterference. Others are nominal without information, accessibility, infrastructure, staff, funding, or enforcement. Increasing depth reveals capacity and allocation decisions, but it must not turn current scarcity into an automatic justification for denial.

Constraint scrutiny rises with irreversibility, coercion, surveillance, bodily impact, exclusion, vulnerability, and power asymmetry. Remedy strength should track breach severity and include actual state-changing authority. Dissent visibility should also rise with contestation: a single adopted interpretation may be necessary for operation, but alternative views and review conditions should not disappear.

The archetype should never tune for tidy matrices alone. A more complete map may expose genuine pluralism, uncertainty, and resource conflict. That apparent messiness is information needed for legitimate governance.

Invariants to Preserve

Preserve relational completeness. Every adopted position must identify bearer, object, type, counterparty consequence, scope, and remedy status. Preserve categorical honesty: a liberty is not silently upgraded to a claim, a technical capability is not treated as legitimate power, and an aspiration is not reported as an enforceable entitlement.

Preserve the distinction between current practice and justified design. An organization may currently exercise power that it lacks legitimate authority to exercise. A system may deny a claim because implementation is absent. The map records both facts without deriving ought from is.

Preserve affected-party visibility, especially for low-power, indirectly affected, future, or collectively represented groups. Preserve capacity and distribution assumptions when positive obligations are involved. Preserve a stable core against exception creep while allowing legitimate, explicit, time-bounded exceptions.

Preserve contestability. The map is an aid to authority, not authority itself. Evidence, value judgments, dissent, uncertainty, and reviewer roles remain visible. Preserve proportionality and least-restrictive reasoning when constraints are imposed. Preserve remedy and transition so rights are not recognized only at the moment of drafting.

Finally, preserve domain humility. The same relational grammar can illuminate software, organizations, contracts, services, and public law, but those domains do not confer the same legal or moral status. Cross-domain reuse is structural analogy, not doctrinal equivalence.

Target Outcomes

The immediate outcome is precise language: participants can say whether they mean permission, noninterference, provision, authority, protection from authority, or remedy. The operational outcome is aligned implementation: policy, code, contracts, staffing, capacity, monitoring, and appeals express compatible positions.

The governance outcome is better conflict handling. Scope clarification resolves false conflicts; true conflicts identify affected parties, duties, burdens, authority, alternatives, and review. Restrictions become narrower and more evidence-linked. Positive claims become more credible because owners, capacity, queues, and remedies are visible.

The equity outcome is not automatic agreement but reduced invisibility. Burdens exported to people outside the focal relationship appear in the interaction matrix. Formal liberties that cannot be exercised because of barriers become distinguishable from provision claims and capacity choices. Remedy gaps are measurable.

The learning outcome is a reusable record of interpretation. Future teams can see why a relation was classified, what alternatives were rejected, what dissent remained, and what changes should trigger review. This reduces repeated category debates and makes silent erosion easier to detect.

Tradeoffs

Precision costs time, expertise, and maintenance. Typed relation maps can feel legalistic, especially in settings accustomed to flexible norms. The remedy is layered representation and proportional depth, not abandonment of counterpart analysis.

Making positive duties explicit can expose promises that exceed capacity. That may create political or organizational conflict, but hiding the conflict creates informal rationing and unreliable claims. Capacity mapping should support phased provision, minimum floors, transparent allocation, and review rather than immediate erasure of the position.

Formal relation typing can underrepresent traditions that frame rights collectively, relationally, culturally, or through responsibilities rather than individual claims. The Collective–Individual Relation Overlay and Dissent Register mitigate this, but expert and community review remain necessary.

Strong remedy and scrutiny improve credibility but can slow decisions. Interim protective measures may be necessary under urgency, with narrow scope, evidence preservation, expiry, notice, and rapid review. Finally, public transparency can conflict with privacy or safety; decision records should disclose reasons and structure while minimizing sensitive data.

Failure Modes

Label inflation is the most common failure. If every interest becomes a right, the map cannot assign coherent priority or duties. Liberty-to-entitlement drift creates unowned provision. Claim-without-duty-bearer produces symbolic rights. Power-as-liberty confusion hides who is exposed to another's decision.

Premature balancing lets actors compare slogans before defining relations. Technical authorization substitution treats existing permissions as proof of legitimacy. Exception erosion preserves formal language while operational protection disappears. Remedy theater creates an appeal that cannot change state, restore access, compensate loss, or prevent retaliation.

Resource concealment turns universal claims into opaque queues and discretionary scarcity. Matrix false neutrality hides value judgments behind tables. Other failures include overclassification, inaccessible process, privacy-invasive mapping, doctrinal overclaim, and importing public-law language into private systems to inflate status.

Detection should be structural. Look for empty counterpart fields, unowned capacity, claims without remedies, powers without liabilities, permissions without warrant, exceptions without expiry, crosswalk gaps, scenario contradictions, and unresolved burdens on absent parties. Failure remediation returns to relation classification and authority, not merely better wording.

Neighbor Distinctions

Procedural Fairness Design governs notice, voice, evidence, impartiality, reasons, and review. Rights–Freedoms Obligation Mapping defines what substantive positions the process is considering. A perfectly fair process can apply an incoherent relation map; a coherent map can still be implemented through an unfair process. Both may be required.

Adjudication Process Design resolves disputes through evidence, standards, decision, remedy, and appeal. This archetype can operate before any dispute, during policy design, or after adjudication reveals a category gap. Proportionality Calibration selects response scale after the protected positions and constraints are known.

Autonomous Action Zone Protection creates a bounded liberty-like domain with noninterference and override rules. It does not classify the full system of claims, powers, immunities, provision duties, and remedies. Informed Consent Governance handles voluntary, informed, specific, authorized, and revocable agreement; it cannot make every protection waivable or create every authority.

Equity Adjustment changes rules or support for relevant differences. Normative Assumption Explicitness exposes value premises. Outside-Authority Influence Channel Mapping finds informal pressure on sovereignty. Each is composable but owns a distinct intervention signature.

Cross-Domain Examples

In a cloud service, an API key grants technical permission, a subscription may create an availability claim, the provider retains a security power to suspend, and the customer may hold an immunity from retroactive pricing changes under a contract. Mapping these relations reveals different notice, evidence, capacity, and remedy requirements.

In a hospital, treatment choice includes liberties against coercion and claims to material information and comprehension support. Access may add positive duties subject to capacity and allocation. Clinical authority includes powers bounded by consent, emergency rules, competence, and review. One “patient rights” page is insufficient without this structure.

In a matrix organization, a team may have liberty to choose implementation, power to deploy within a boundary, duty to meet shared controls, liability to a valid security override, and immunity from unrelated functional veto. Decision-rights mapping prevents autonomy rhetoric from hiding centralized control.

In public policy, a time-and-place restriction can be evaluated only after identifying the protected liberty, safety claims, duty bearers, authority, evidence, geographic and temporal scope, unequal burden, alternatives, remedy, and sunset. In education, participation and fair assessment claims require accessibility duties while academic integrity constrains acceptable alternatives.

Non-Examples

A grievance panel that needs better notice and evidence rules is a Procedural Fairness or Adjudication problem unless the underlying relation is also ambiguous. A regulator selecting sanction severity needs Proportionality Calibration. A research team improving an opt-in flow needs Informed Consent Governance. A unit seeking permissionless execution within a charter needs Autonomous Action Zone Protection.

A philosopher comparing theories without an implementation decision is not yet applying this solution archetype. A security engineer adding a role to an access-control list is using a mechanism unless substantive entitlement and authority are disputed. A workshop that merely asks participants to rank values without counterpart duties, scope, remedy, or translation is not Rights–Freedoms Obligation Mapping.

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

• Normativity: What ought to be.
• Property Rights: An enforceable bundle of exclusive entitlements over a resource.
• Rights vs. Freedoms: Claims vs liberties.

Also references 16 related abstractions

• Accountability: Responsibility for actions.
• Adjudication (Dispute Resolution): Dispute resolution.
• Authority: The recognized, legitimate right to issue binding decisions within a defined scope, distinct from raw coercive force or mere persuasive influence.
• Balance: Even distribution of elements.
• Boundary: Defines system limits.
• Consent: Voluntary agreement.
• Constraint: Limits possibilities to guide outcomes.
• Delegation of Authority: Assign responsibility.
• Equity: Context-sensitive fairness.
• Fairness: Judging whether an allocation or procedure treats comparable parties impartially according to a defensible standard, given that multiple such standards can conflict.

▸ Show 6 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Public-Policy Rights–Obligation Mapping · domain variant · recognized

Maps public claims, liberties, state duties, powers, immunities, constraints, and remedies across affected populations and institutions.

• Distinct from parent: Adds public authority, legislative mandate, state capacity, non-derogation, public reason, and cross-jurisdiction review.
• Use when: Public authority defines or restricts protected positions; Multiple populations and institutions are affected; Provision and noninterference duties interact; Independent review is available.
• Typical domains: public policy, civil rights, public health, education policy, housing
• Common mechanisms: hohfeldian relation matrix, rights conflict scenario table, least restrictive alternative screen, proportionality balancing record

Digital Permission–Entitlement Mapping · implementation variant · recognized

Translates user, operator, owner, and regulator positions into permissions, prohibitions, service commitments, powers, immunities, audit, and remedy paths.

• Distinct from parent: Adds executable policy translation, identity lifecycle, system states, logging, code review, and failure recovery.
• Use when: Software permissions implement policy positions; Service access and capability are distinct; Automated enforcement can alter positions; Technical and policy owners need traceability.
• Typical domains: access control, digital platforms, cloud services, data governance, automated decision systems
• Common mechanisms: claim liberty classification tree, counterparty obligation register, permission entitlement crosswalk, remedy traceability review

Organizational Decision-Rights Mapping · domain variant · recognized

Maps who may decide, who must be consulted or informed, who can veto or review, and what duties accompany organizational authority.

• Distinct from parent: Adds organizational roles, operating cadence, delegated authority, succession, and performance accountability.
• Use when: Roles have overlapping mandates; Delegation and autonomy conflict; Decision rights need counterpart accountability; Escalation and review are unclear.
• Typical domains: corporate governance, matrix organizations, partnerships, incident management, public administration
• Common mechanisms: hohfeldian relation matrix, counterparty obligation register, rights conflict scenario table, permission entitlement crosswalk

Positive–Negative Rights Capacity Mapping · structural variant · recognized

Separates noninterference duties from provision, access, capacity, funding, and enforcement duties required for effective exercise.

• Distinct from parent: Deepens positive obligation feasibility and the interface between formal liberty and effective capability.
• Use when: A nominal freedom may be unusable without provision; Resources or service capacity are finite; Universal language hides queue or rationing rules; Equity and accessibility affect effective exercise.
• Typical domains: healthcare access, disability access, education, public services, infrastructure
• Common mechanisms: claim liberty classification tree, counterparty obligation register, rights conflict scenario table, proportionality balancing record

Near names: Claim Rights vs. Liberties Mapping, Hohfeldian Rights Analysis, Decision-Rights Matrix.

Editorial Notes

Problem Classification

Classification: Authority, Accountability, Legitimacy & Fair-Process Failure → Rules, Rights, Obligations & Consistency

Problem kernel: rights language omits bearers counterparties duties and remedies

Rationale: Earliest causal condition: A policy, contract, platform rule, organizational mandate, or public controversy uses “right,” “freedom,” “permission,” “entitlement,” “choice,” and “duty” as if they were interchangeable. The statement omits the relation's bearer, counterparty, object, jurisdiction, conditions, costs, exceptions, or remedy. Competing actors then debate abstractions while implementing incompatible assumptions: a liberty is treated as

Independent corroboration: The earliest necessary condition in the frozen evidence is: A policy, contract, platform rule, organizational mandate, or public controversy uses “right,” “freedom,” “permission,” “entitlement,” “choice,” and “duty” as if they were interchangeable. That is a rules rights obligations and consistency problem because Durable cooperation fails because constitutive acts, roles, rights, duties, ownership incidents, and enforcement rules are unstable, selectively binding, underspecified, or unable to reproduce order.

Review outcome: Independent reviewer agreement; high confidence.