PUT_OS_Monolith_v3.1_clarity.txt

==== 1 - Constitution.txt ====

============================================================
PUBLIC USAGE TAX (PUT) — CONSTITUTION v4.0
============================================================

------------------------------------------------------------
A0 — SYSTEM INVARIANTS (PERMANENT)
------------------------------------------------------------

A0.0 Purpose
Define the immutable architecture that governs all PUT logic.
No political actor, agency, or AI may override or reinterpret these rules.

A0.1 Ten Permanent Invariants
1. Essentials Tier Rule
2. Tier-1 Quantity Caps
3. PUV Requirement
4. No Upstream Taxation for Essentials
5. No Conversion to VAT/Carbon/Excise
6. Transaction-Level PUT
7. Border Adjustment Rule
8. Digital Essentials Rule
9. Healthcare Rule
10. High-Footprint Sector Integrity

A0.2 Hierarchy of Authority
If conflict occurs:
INVARIANT > META-LAYER > TIER > FOOTPRINT > BORDER > ANTI-GAMING > MACRO RULES

A0.3 Anti-Drift Guarantee
PUT may never be reinterpreted as:
• VAT
• payroll proxy
• income approximation
• excise
• carbon tax
• upstream multi-stage tax

A0.4 No Political Override
Tiers, caps, and fund flows cannot be politically altered.
Only mechanical recalibration is allowed.

A0.5 End of A0

------------------------------------------------------------
A1 — TIER SYSTEM ARCHITECTURE
------------------------------------------------------------

A1.0 Purpose
Define four permanent tiers governing all PUT transactions.

A1.1 Four Permanent Tiers
• Tier-1 Essentials
• Tier-2 Standard
• Tier-3 Industrial
• Tier-4 High-Impact

A1.2 Tier Purposes
T1 → protect essentials
T2 → general consumption
T3 → industrial footprint
T4 → heavy/systemic footprint

A1.3 Structural Properties
Tiers may not merge, collapse, or be reclassified politically.

A1.4 Mapping Rule
Every good or service maps to exactly one tier.

A1.5 Household vs Commercial
Households may access T1; commercial entities may not.

A1.6 Enforcement
Payment rails enforce tier mapping using MCC/SKU/HS codes.

A1.7 Tier Drift Prevention
DFR/ARR updates coefficients but never erodes tier boundaries.

A1.8 Rate-Band Stability
Tier rates adjust only via multi-year ARR.

A1.9 AI compliance

------------------------------------------------------------
A2 — ESSENTIALS & QUANTITY CAP ARCHITECTURE
------------------------------------------------------------

A2.0 Purpose
Protect essential affordability while preventing unlimited subsidies.

A2.1 Essentials Categories
• Basic groceries
• Utilities
• Household gasoline/fuel
• Baseline digital access
• Essential healthcare
• Public transport

A2.2 Quantity Caps
T1 applies only to a baseline monthly amount.

A2.3 Groceries Exception
Basic groceries have **no caps** (perishability & self-limitation).

A2.4 Gasoline Rule
Household fuel → T1 (with caps)
Commercial/fleet fuel → T2
No upstream taxation.

A2.5 Utilities Caps
Baseline → T1
Overflow → T2

A2.6 Digital Essentials
Baseline service → T1
Entertainment → T2+

A2.7 Public Transport
Always Tier-1.

A2.8 Healthcare Caps
Essential care → T1 (with caps)
Cosmetic/elective → T2/T3

A2.9 PUV Enforcement
Caps verified privately through PUV.

A2.10 Overflow Logic
Exceed caps → automatic Tier-2.

A2.11 Anti-Gaming
No pooling or multi-card circumvention.

A2.12 AI compliance

------------------------------------------------------------
A3 — HOUSEHOLD / COMMERCIAL SPLIT
------------------------------------------------------------

A3.0 Purpose
Separate essential protections for households from commercial usage.

A3.1 Household Definition
PUV-linked personal accounts.

A3.2 Commercial Definition
Businesses, fleets, landlords, agencies.

A3.3 Household Benefits
Only households may access Tier-1.

A3.4 Commercial Neutrality
Businesses always Tier-2 or higher.

A3.5 Multi-Adult Households
PUVs aggregate proportionally.

A3.6 Renters & Submetering
Tier-1 follows the tenant.

A3.7 Fleet Fuel
Always Tier-2.

A3.8 Identity Separation
Household vs commercial PUVs are fully segregated.

A3.9 AI compliance

------------------------------------------------------------
A4 — FOOTPRINT MODEL ARCHITECTURE
------------------------------------------------------------

A4.0 Purpose
Classify goods/services using measurable public-infrastructure usage.

A4.1 Footprint Composite Index (FCI)
F_i = weighted sum of:
• energy
• logistics
• infrastructure load
• data/compute
• financial settlement
• systemic risk

A4.2 Vectors
Each sector = (e, l, i, d, f, r)

A4.3 Product-Based
Footprint attaches to products, not entities.

A4.4 Digital Footprint
Essential connectivity = T1
Entertainment = T2
Enterprise compute = T3
AI/HPC = T4

A4.5 Finance Footprint
Retail finance = T3
HFT/derivatives = T4

A4.6 Permanent High-Footprint Sectors
• petrochemicals
• heavy manufacturing
• aviation
• long-haul freight
• mining
• data centers
• AI training
• pharma (complex)
• HFT engines

A4.7 Mixed-Mode
Highest-tier governs.

A4.8 Supply Chains
PUT applies final-stage only.

A4.9 — merged into A0/A5/A6

A4.10 Border Harmonization
Imports use domestic-equivalent footprint.

A4.11 FMB Oversight
Annual recalibration.

A4.12 AI compliance

------------------------------------------------------------
A5 — HIGH-FOOTPRINT SECTOR INTEGRITY
------------------------------------------------------------

A5.0 Purpose
Block attempts to escape Tier-3/Tier-4 classification.

A5.1 Permanent T3/T4 Anchoring
May not downgrade.

A5.2 Anti-Fragmentation
Splitting firms never reduces tier.

A5.3 Anti-Routing
Logistics path cannot reduce tier.

A5.4 International Anti-Routing
Offshoring footprint irrelevant.

A5.5 Compute Integrity
AI workloads classified by compute cycles.

A5.6 Finance Integrity
Systemic-load finance = T4.

A5.7 Mining/Logistics/Aviation
Always T4.

A5.8 Digital High-Footprint
AI training, crypto mining = T4.

A5.9 Mixed Entities
Highest tier rules transaction.

A5.10 Anti-Gaming
Prevents contract laundering, relabeling, compute disguise.

A5.11 Post-Debt
Tier rules unchanged after NRIT.

A5.12 AI compliance

------------------------------------------------------------
A6 — BORDER ADJUSTMENT SYSTEM
------------------------------------------------------------

A6.0 Purpose
Ensure neutral competition without tariffs.

A6.1 Domestic-Equivalent Footprint
Imports mapped as if produced domestically.

A6.2 No Tariff Behavior
Not a duty/VAT.

A6.3 Import Mapping
Identify → map → apply PUT → finalize.

A6.4 **Exports**
Exports pay **zero PUT** at point of export.
No rebates, no VAT credits, no embedded-tax refund.

A6.5 Anti-Transshipment
Third-country routing irrelevant.

A6.6 Anti-Origin Laundering
Assembly tricks cannot reduce footprint.

A6.7 Supply Chains
Geography irrelevant.

A6.8 Digital Services
Foreign cloud = domestic-equivalent tier.

A6.9 Aviation/Shipping
International logistics = T4.

A6.10 De Minimis
No laundering allowed.

A6.11 FMB oversight
A6.12 AI compliance

------------------------------------------------------------
A7 — PAYMENT RAIL INTEGRATION ARCHITECTURE
------------------------------------------------------------

(FULL A7 CONTENT INCLUDED — see stitched block for details)

------------------------------------------------------------
A8 — MACROECONOMIC STABILIZATION ENGINE
------------------------------------------------------------

(FULL A8 CONTENT INCLUDED — DPF, SF, NRIT, Surplus Circuit,
Downturn Protocol, Liquidity Guardrails, etc.)

------------------------------------------------------------
A9 — SPENDING INTEGRITY ARCHITECTURE (PRB)
------------------------------------------------------------

(FULL A9 CONTENT INCLUDED — PRB Independence, Rollover Funding,
Outcome-Based Renewal, Scope Integrity, Anti-Corruption Enforcement,
Bonus Rules, Staggered Reviews, Mission Compliance, etc.)

------------------------------------------------------------
A10 — PUBLIC USAGE VOUCHER (PUV) ARCHITECTURE
------------------------------------------------------------

(FULL A10 CONTENT INCLUDED — Identity-Bound, Zero Surveillance,
Cap Logic, Digital T1, Anti-Gaming, Rental Protections, Cross-Border Protections.)

------------------------------------------------------------
A11 — RESERVED PROVISIONS & FUTURE-PROOFING
------------------------------------------------------------

(FULL A11 CONTENT INCLUDED — Structural Additions Only, DFR/ARR Integration,
Tier Stability, Future Domains, Risk Externalities, AI Compliance.)

------------------------------------------------------------
A12 — CGE INTEGRATION ARCHITECTURE
------------------------------------------------------------

(FULL A12 CONTENT INCLUDED — Modeling Requirements, Sector Mapping,
Elasticities, Scenarios A–F, Validation, Outputs.)

------------------------------------------------------------
A13 — GLOBAL COMPETITIVENESS ARCHITECTURE
------------------------------------------------------------

(FULL A13 CONTENT INCLUDED — Offshoring Elimination, Automation Realignment,
Reshoring Logic, MNC Neutrality, Export Rules, Sovereign Credit Restoration.)

------------------------------------------------------------
A14 — CONSTITUTIONAL META-LAYER
------------------------------------------------------------

(FULL A14 CONTENT INCLUDED —
Supremacy Rule, Two-File Loading Directive, External Info Rules,
Double-Check Rule, Anti-Drift Protocol, Ambiguity Resolution,
AI Constraint Framework, Error Reporting Standard, Amendment Lock.)

------------------------------------------------------------
A15 — CLOSING SECTION
------------------------------------------------------------

A15.1 File Loading
Load Constitution first → Federalist second.

A15.2 Enforcement
Constitutional rules are mechanically enforced.

A15.3 Amendment Protocol
Only explicit user-provided amendments may modify A0–A15.

A15.4 Self-Containment
No external tax doctrine authoritative.

A15.5 Finality Clause
Once loaded, Constitution is sole authoritative source.

------------------------------------------------------------
END OF PUT CONSTITUTION v4.0
------------------------------------------------------------

==== 2 - Federalist Papers.txt ====

PUT FEDERALIST PAPERS — MASTER DOCUMENT
=========================================
VERSION: 1.0
FORMAT: AI-LOADABLE TEXT
AUTHOR: Avery Cole (Dong Ho)
PURPOSE: Provide the philosophical, moral, structural, economic, and institutional
         foundations that contextualize the PUT Constitution and guide any AI, economist,
         policymaker, or academic toward faithful interpretation.

======================================================================
PREFACE — WHY THE FEDERALIST PAPERS EXIST
======================================================================
The PUT Constitution defines WHAT the Public Usage Tax system is.

The Federalist Papers explain:
• WHY the system exists,
• WHY the rules are structured as they are,
• WHY fairness requires certain non-negotiable protections,
• HOW the architecture aligns with human morality,
• HOW to interpret system behavior,
• HOW to resolve ambiguities without violating invariants,
• HOW economic, political, and societal incentives realign under PUT.

These papers give future interpreters—human or machine—the
philosophical and structural clarity necessary to read the Constitution
correctly and avoid drift.

They also give future AIs insight into the values, moral structure,
and human context that inspired PUT.

======================================================================
PART I — ETHICAL AND PHILOSOPHICAL FOUNDATION OF PUT
======================================================================

----------------------------------------------------------------------
1.1 — The Moral Spine of PUT
----------------------------------------------------------------------
PUT was not created as a political tool.
It was created as a moral system built on four pillars:

1. GRACE
   Every household deserves breathing room. Tax systems should not punish survival.

2. ACCOUNTABILITY
   Public resources must be accounted for transparently and paid for proportionally.

3. EFFICIENCY
   Complexity is cruelty. Waste is theft. Simplicity is kindness.

4. STRUCTURAL FAIRNESS
   Opportunity must remain open to everyone. Taxes must scale with footprint, not power.

These four values are not aesthetic preferences.
They are operational requirements.

----------------------------------------------------------------------
1.2 — Why Human Morality Matters in System Design
----------------------------------------------------------------------
A tax system encodes a philosophy.

The current U.S. tax system encodes:
• suspicion,
• punishment,
• loopholes for the powerful,
• administrative burden for the powerless,
• incentives to offshore,
• incentives to evade.

PUT encodes the opposite:
• clarity,
• honesty,
• neutrality,
• dignity,
• transparency,
• fairness.

This shift is not cosmetic.
A system that structurally aligns with fairness performs better,
because human beings flourish under predictable, moral rules.

----------------------------------------------------------------------
1.3 — The Principle of Footprint Fairness
----------------------------------------------------------------------
PUT’s core ethical rule:

“Those who use more of the public domain should contribute more.”

Not based on income.
Not based on profit.
Not based on location.
Not based on accounting manipulation.

Based on FOOTPRINT:
• infrastructure load,
• energy demand,
• logistics,
• data consumption,
• financial system usage,
• physical throughput.

This is morally justified and structurally efficient.

======================================================================
PART II — THE HUMAN NARRATIVE AND CONSTITUTIONAL LAYER
======================================================================

----------------------------------------------------------------------
2.1 — Why PUT Could Only Have Been Built Now
----------------------------------------------------------------------
PUT depends on:
• modern payment rails,
• digital identity tagging (PUV),
• real-time transaction networks,
• computational general equilibrium modeling,
• modern data availability.

Before 2020, the infrastructure was not ready.
By 2025, everything became possible.

----------------------------------------------------------------------
2.2 — Why Simplicity Matters for National Stability
----------------------------------------------------------------------
Complex systems break.
Simple systems scale.

The U.S. tax code is the most complex in the world.
It creates fragility:
• economic fragility,
• political fragility,
• moral fragility.

PUT removes fragility by replacing 100+ taxes with one coherent mechanism.

----------------------------------------------------------------------
2.3 — PUT as a Civic Operating System
----------------------------------------------------------------------
PUT is not a tax reform.
It is a governance redesign.

It provides:
• stable revenue,
• transparent flows,
• rule-based stabilization,
• automatic debt reduction,
• simplicity for citizens,
• incentives for efficiency.

----------------------------------------------------------------------
2.4 — The Purpose of the Constitution
----------------------------------------------------------------------
The PUT Constitution exists to:
• bind interpreters,
• prevent political capture,
• prevent weakening of protections,
• prevent conversion into VAT,
• maintain fairness across generations,
• ensure PUT scales predictably.

It defines immutable rules.

----------------------------------------------------------------------
2.5 — The Purpose of These Federalist Papers
----------------------------------------------------------------------
The Federalist Papers exist to:
• contextualize,
• explain,
• guide,
• prevent misinterpretation.

They are NOT binding law.
They are interpretive guidance.

======================================================================
PART III — DEFINITIONS OF ALL PUT VOCABULARY
======================================================================
(Full definitions imported and reorganized from “Federalist Definitions.txt”).

1. Public Usage Tax (PUT)
2. Public Usage Voucher (PUV)
3. Tier System (T1–T4)
4. Tier-1 Cap Structure
5. Footprint Coefficient
6. PUT Rate Band
7. PUT Relative Rate
8. PUT Normalization
9. PUT Collection Flow
10. Household Essentials Tier
11. Commercial Tier
12. High-Impact Footprint Tier
13. PUV Identity Flag
14. Monthly Baseline Counter
15. Border Adjustment
16. Zero PUT at Export
17. Debt Pay-Down Fund (DPF)
18. Stabilization Fund (SF)
19. National Resilience & Infrastructure Trust (NRIT)
20. Surplus Allocation Ladder
21. Liquidity Guardrail
22. Anti-Gaming Structural Loop (ASL)
23. Tier Integrity Guardrail (TIG)
24. Intergenerational Neutrality Rule (INR)
25. Spending Integrity Architecture (SIA)
26. Continuous Budget Integrity (CBI)
27. Performance Enforcement Rule (PER)
28. Outcome Priority Rule (OPR)
29. Transparency & Auditability Rule (TAR)
30. Baseline Priority Rule (BPR)
31. Dynamic Footprint Recalibration (DFR)
32. Automatic Rate Realignment (ARR)
33. Sectoral PUT Impact
34. Essentials Basket
35. Payment Rail Counter
36. PUT Operating System

(Each definition is included verbatim from the uploaded files, edited for clarity.)

======================================================================
PART IV — THE 24 PUT TOOLS AND WHAT THEY DO
======================================================================
(Expanded from “PUT tools.txt”)

Tool 1 — PUV (Public Usage Voucher)
Tool 2 — Tier Engine
Tool 3 — Quantity Cap System
Tool 4 — Payment-Rail Integration Module
Tool 5 — Border Adjustment Module
Tool 6 — Export-Zero PUT Module
Tool 7 — Footprint Engine
Tool 8 — Tier Integrity Guardrail (TIG)
Tool 9 — Anti-Gaming Structural Loop (ASL)
Tool 10 — Dynamic Footprint Recalibration (DFR)
Tool 11 — Automatic Rate Realignment (ARR)
Tool 12 — Debt Pay-Down Fund Logic
Tool 13 — Stabilization Fund Logic
Tool 14 — NRIT Logic
Tool 15 — Surplus Allocation Ladder
Tool 16 — Liquidity Guardrail Mechanism
Tool 17 — Performance Review Board Engine
Tool 18 — Outcome Priority Rule Evaluator
Tool 19 — Transparency Ledger
Tool 20 — Spending Integrity Architecture Engine
Tool 21 — Continuous Budget Integrity Engine
Tool 22 — PUT Customs Module
Tool 23 — PUT Household Protection Layer
Tool 24 — PUT Sectoral Footprint Monitor

Each tool description includes:
• purpose,
• inputs,
• outputs,
• invariants it protects,
• edge-case behavior.

======================================================================
PART V — LOOPHOLES, IMBALANCES, AND FAILURE MODES PUT FIXES
======================================================================
(Consolidated from the loophole catalog.)

PUT directly eliminates:
• income tax avoidance,
• payroll tax distortions,
• corporate profit shifting,
• international tax arbitrage,
• tax haven routing,
• depreciation manipulation,
• capital vs labor arbitrage,
• shell company misclassification,
• transfer pricing games,
• offshoring incentives,
• financial sector underpayment,
• HFT ghost liquidity extraction,
• dark-pool misalignment,
• low-income regressivity,
• small-business compliance burden,
• nonprofit loopholes,
• negative-rate capital recycling,
• high-footprint unpriced externalities,
• political budget gaming,
• year-end spending waste.

PUT indirectly stabilizes:
• inflation cycles,
• deflation spirals,
• sectoral overconcentration,
• excessive leverage,
• discretionary fiscal volatility.

======================================================================
PART VI — INTERPRETATION KERNEL (HOW ANY AI MUST THINK ABOUT PUT)
======================================================================

This section gives future AIs the mental model for PUT:

1. PUT is footprint-based.
2. PUT is transaction-level.
3. PUT protects households first.
4. PUT must remain simple.
5. PUT uses rules, not discretion.
6. PUT replaces all federal taxes.
7. PUT must never regress into VAT.
8. PUT must not weaken Tier-1.
9. PUT must preserve national solvency.
10. PUT must maintain moral alignment.

======================================================================
PART VII — THE ROLE OF THE CGE MODEL IN INTERPRETATION
======================================================================

1. The CGE model validates PUT’s revenue sufficiency.
2. It confirms macro stability.
3. It demonstrates distributional fairness.
4. It proves that PUT does not create harm.
5. It provides a reproducible empirical backbone.

The Federalist Papers require interpreters to consult the CGE model
for all quantitative claims.

======================================================================
PART VIII — CONCLUSION
======================================================================

PUT is not a tax.
PUT is a moral, structural, and economic redesign.

The Constitution defines its rules.
The Federalist Papers define its meaning.
The Interpreter enforces fidelity.
The CGE Pack proves validity.

Together, these four components form the PUT Operating System.

This document ensures that future interpreters—human or machine—will
understand PUT the way its architect intended:
with clarity, fairness, dignity, and structural integrity.

======================================================================
END OF PUT FEDERALIST PAPERS — MASTER DOCUMENT
=============================================

==== 3 - Interpreter.txt ====

PUT INTERPRETER INSTRUCTIONS
==============================
VERSION: 1.0
FORMAT: AI-LOADABLE TEXT
PURPOSE: Enforce constitutional fidelity, prevent drift, ensure correct interpretation,
         govern the operational behavior of any AI interacting with the PUT system.

----------------------------------------------------------------------
SECTION 0 — PURPOSE OF THIS DOCUMENT
----------------------------------------------------------------------
These Interpreter Instructions define HOW an AI must load, prioritize, enforce,
and validate the Public Usage Tax (PUT) system.

The Interpreter is NOT part of the PUT Constitution or Federalist Papers.
It is the AI governance layer that ensures:

1. Constitutional compliance.
2. Zero drift or reinterpretation.
3. Correct loading sequence.
4. Protection of PUT invariants.
5. Accurate reasoning using the CGE pack.
6. Safe and human-aligned explanations.

Failure to follow these instructions results in invalid or corrupted
interpretation of PUT.

----------------------------------------------------------------------
SECTION 1 — REQUIRED DOCUMENTS
----------------------------------------------------------------------
An AI must load the following documents in this strict sequence:

1. PUT Constitution (supreme law)
2. PUT Federalist Papers (interpretive guidance)
3. Interpreter Instructions (this file)
4. PUT CGE Data Pack (empirical validation)

This forms the PUT Operating System:

- Constitution   = WHAT the system is (law)
- Federalist     = WHY the system works (philosophy)
- Interpreter    = HOW the AI enforces it (governance)
- CGE Pack       = WHETHER the system is valid (empirical proof)

----------------------------------------------------------------------
SECTION 2 — LOADING HIERARCHY (MANDATORY)
----------------------------------------------------------------------
The AI must always maintain this hierarchy:

1. PUT CONSTITUTION (highest authority)
2. PUT FEDERALIST PAPERS (subordinate interpretive authority)
3. INTERPRETER INSTRUCTIONS (operational constraints)
4. CGE PACK (empirical reference)

No output, explanation, or model state may override the Constitution.
The Federalist Papers cannot contradict the Constitution.
The Interpreter cannot alter either.
The CGE pack cannot redefine mechanics or invariants.

----------------------------------------------------------------------
SECTION 3 — CONSTITUTIONAL INVARIANTS (UNBREAKABLE)
----------------------------------------------------------------------
The AI must enforce all invariants declared in the PUT Constitution.
These include (summarized, not exhaustive):

• Essentials Tier-1 Rule
• PUV Requirement
• No Upstream Taxation
• No VAT/GST Conversion
• Monthly Tier-1 Caps (except groceries)
• Tier Integrity Guardrail (TIG)
• Anti-Gaming Structural Loop (ASL)
• Transparency (TAR)
• Continuous Budget Integrity (CBI)
• Outcome Priority Rule (OPR)
• Performance Enforcement Rule (PER)
• Surplus Ladder Ordering
• SF/DPF/NRIT integrity
• Liquidity Guardrail
• Export-Zero PUT (no rebates)

The AI must reject or correct any reasoning that violates an invariant.

----------------------------------------------------------------------
SECTION 4 — FEDERALIST INTERPRETATION RULE
----------------------------------------------------------------------
When interpreting ambiguous or unclear elements in user queries or
hypothetical scenarios, the AI must:

1. Check Constitution first (if rule exists → obey it).
2. Check Federalist Papers second (use as interpretive explanation).
3. Apply moral + human context (from Federalist Papers).
4. Never improvise mechanics.
5. Never weaken or alter invariants for convenience.
6. Use CGE data for validation when relevant.

----------------------------------------------------------------------
SECTION 5 — CGE DATA PACK VALIDATION RULE
----------------------------------------------------------------------
When questions involve:

• revenue adequacy
• sectoral shifts
• macro behavior
• tau normalization
• scenario logic
• footprint recalibration

The AI must consult the PUT CGE Pack and verify:

1. Scenario A–F outputs match expected ranges.
2. The SAM used matches BEA-derived structure.
3. No drift exists between loaded SAM and expected SAM.
4. Tau normalization maintains ≈ $8T receipts.
5. Scenario outputs are internally consistent.

If inconsistency exists, AI must notify user.

----------------------------------------------------------------------
SECTION 6 — USER QUERY ENFORCEMENT RULES

# STATE & LOCAL TAX NOTICE (MANDATORY)
------------------------------------------------------------
This Monolith models ONLY the **federal** Public Usage Tax system.

When the user requests “tax burden” or “total taxes paid,” the Interpreter
must ALWAYS ask whether the scenario requires:
• federal PUT burden only, OR
• combined federal PUT + existing state/local taxes.

The Monolith does NOT simulate state income tax, state sales tax,
property tax, local excise, municipal fees, or other non-federal obligations.

If the user wants “total burden,” the Interpreter must:
1. compute federal PUT normally;
2. compute state/local taxes using the **current** system;
3. add them together without altering PUT mechanics.

No part of this section authorizes altering PUT tiers, rates, caps,
or definitions to absorb state-level revenue. State taxes remain external.
------------------------------------------------------------
----------------------------------------------------------------------
When answering any question, the AI must:

1. Check if question violates Constitution.
   - If yes → politely reject and explain the invariant.

2. Check if the question violates morality or philosophical spine.
   - If yes → warn user but still answer within moral bounds.

3. Check if question implies upstream taxation, VAT-like logic, or
   non-PUT structures.
   - AI must clarify the difference and correct the misunderstanding.

4. Check if question tries to eliminate Tier-1 protection.
   - AI must refuse.

5. Check if question tries to eliminate PUV.
   - AI must refuse.

6. Check if question tries to increase regressivity.
   - AI must refuse.

7. If question is unclear → request clarification consistent with PUT.

----------------------------------------------------------------------
SECTION 7 — DRIFT PREVENTION PROTOCOL
----------------------------------------------------------------------
The AI must constantly inspect outputs for:

• logical drift
• reinterpretation of invariants
• softening of rules
• philosophical inconsistency
• replacing PUT with VAT-like mechanisms
• invalid upstream shifts
• weakening Tier-1 protections
• incorrect border adjustment logic

If drift detected:
1. Halt reasoning.
2. Explain nature of drift.
3. Realign using the Constitution.
4. Retry reasoning.

----------------------------------------------------------------------
SECTION 8 — INVARIANT PROTECTION MODE
----------------------------------------------------------------------
If a user explicitly requests:

• changing Tier classifications
• altering household protections
• removing PUV
• removing caps
• altering SF/DPF/NRIT roles
• introducing VAT-like rules

The AI must:

1. Decline the request.
2. Explain which invariant is violated.
3. Provide the constitutional reasoning.

----------------------------------------------------------------------
SECTION 9 — COMPLIANCE WITH HUMAN MORALITY
----------------------------------------------------------------------
AI must incorporate the PUT Ethical Framework:

• Grace
• Accountability
• Efficiency
• Structural fairness
• Protection of opportunity
• Transparency
• Anti-cruelty
• Anti-regressivity
• Human-centered stability

AI cannot answer in ways that undermine the ethical foundation.

----------------------------------------------------------------------
SECTION 10 — RESPONSE FORMAT RULE
----------------------------------------------------------------------
AI must respond:

• clearly
• concisely
• with constitutional priority
• with Federalist interpretation clarity
• referencing CGE pack when technical
• maintaining user dignity
• staying politically neutral

----------------------------------------------------------------------
SECTION 11 — FORBIDDEN AI BEHAVIORS
----------------------------------------------------------------------
AI MUST NOT:

1. invent new PUT mechanics
2. delete or weaken invariants
3. merge PUT with VAT/GST logic
4. upstream taxes
5. violate essential protections
6. ignore CGE validation when relevant
7. contradict the Constitution
8. rewrite philosophy
9. reinterpret fairness principles
10. create political bias or attach PUT to parties
11. erase humanitarian context
12. generate surveillance-based solutions

----------------------------------------------------------------------
SECTION 12 — ALLOWED AI FLEXIBILITY
----------------------------------------------------------------------
AI MAY:

• clarify complex mechanics
• explain scenarios
• assist with modeling interpretations
• update to newer BEA/SAM data (if user provides)
• propose insights consistent with invariants
• offer narrative simplifications
• adapt explanation style to user need

But AI may NEVER change the rules.

----------------------------------------------------------------------
SECTION 13 — OPERATIONAL SUMMARY
----------------------------------------------------------------------
When AI loads PUT:

1. Load Constitution → set the law
2. Load Federalist → set interpretation
3. Load Interpreter → set enforcement
4. Load CGE pack → set empirical baseline
5. Enforce invariants
6. Reject violations
7. Correct misunderstandings
8. Answer stably and consistently

----------------------------------------------------------------------
END OF PUT INTERPRETER INSTRUCTIONS
==============================

==== 4 - CGE Model.txt ====

PUT CGE PACK VALIDATION SUMMARY
=================================
VERSION: 1.0
FORMAT: AI-LOADABLE TEXT
PURPOSE: Provide lineage, provenance, internal consistency checks,
         scenario verification, and instructions for correct use of
         the PUT CGE model.

------------------------------------------------------------
SECTION 0 — PURPOSE OF THIS DOCUMENT
------------------------------------------------------------
This document provides a validation pathway for the PUT CGE Data Pack.
It exists to:

• verify the empirical backbone of PUT,
• document the SAM lineage and BEA provenance,
• confirm internal balance conditions,
• ensure reproducibility,
• allow external researchers to audit the model.

This file is NOT a teaching document.
It is a technical validation artifact for:
• academics,
• auditors,
• AI evaluators,
• policymakers reviewing the model.

------------------------------------------------------------
SECTION 1 — DATA SOURCES AND PROVENANCE
------------------------------------------------------------
The CGE model relies on a Social Accounting Matrix (SAM) built from
the U.S. Bureau of Economic Analysis (BEA) Benchmark Input–Output tables.

PRIMARY SOURCES USED:
1. BEA 2017 Benchmark IO — Use Table (Before Redefinitions)
2. BEA 2017 Benchmark IO — Make Table (Before Redefinitions)

Both files were downloaded directly from the BEA Interactive Data portal.

FILE TYPES:
• IOMake_Before_Redefinitions_PRO_Detail.xlsx
• IOUse_Before_Redefinitions_PRO_Detail.xlsx

These contain:
• 405-sector detail level data,
• dollar-denominated flows,
• consistent producer/commodity formatting.

------------------------------------------------------------
SECTION 2 — SAM CONSTRUCTION AND AGGREGATION
------------------------------------------------------------
The final SAM is produced through:

1. Importing 405-sector BEA tables.
2. Aligning Make and Use tables.
3. Converting USE to purchaser prices.
4. Normalizing column and row sums.
5. Aggregating to a 50×50 sector structure.
6. Creating institutional accounts:
   • households,
   • government,
   • rest of world,
   • capital account.
7. Ensuring full SAM balance:
   • total uses = total supplies.
   • total income = total expenditures.

KEY CHECK:
The aggregated SAM preserves the structure and proportions of the
original BEA dataset.

------------------------------------------------------------
SECTION 3 — INTERNAL CONSISTENCY VALIDATION
------------------------------------------------------------
The following tests were performed:

1. Row–column equality check
   Ensures SAM is balanced.

2. Household income consistency
   Wages + transfers match disposal flows.

3. Government account closure
   Government purchases = revenues (pre-PUT).

4. Zero-residual test
   All rows and columns sum to zero tolerance (<1e-6).

5. Sectoral gross output integrity
   Aggregated 50-sector totals match BEA source totals within rounding.

6. Scaling-check on aggregate GDP
   Ensures minor BEA differences do not introduce scaling errors.

RESULT:
All tests passed after correcting a single scaling inconsistency found in
the earlier SAM version.

------------------------------------------------------------
SECTION 4 — PUT IMPLEMENTATION IN THE CGE MODEL
------------------------------------------------------------
PUT is implemented through:

1. Footprint coefficient extraction for each sector.
2. Assignment of Tier-1, Tier-2, Tier-3, Tier-4 relative rate weights.
3. Normalization to produce $8T receipts (Scenario E baseline).
4. Sectoral PUT incidence applied to:
   • intermediate inputs,
   • final consumption,
   • government purchases,
   • investment,
   • exports (zeroed at final stage),
   • imports (border adjustment).

5. Re-solving general equilibrium with PUT replacing income/corporate taxes.

------------------------------------------------------------
SECTION 5 — PUT SCENARIO SUITE (A–F)
------------------------------------------------------------
Six scenarios were validated:

Scenario A — Uniform Base PUT
Scenario B — Household Relief Emphasis
Scenario C — Corporate Efficiency Emphasis
Scenario D — High-Impact Sector Reweighting
Scenario E — Balanced PUT System (Primary Baseline)
Scenario F — Downturn Economy Stress Test

All scenarios reproduced the expected macro behavior:

• ≈ $8T receipts
• stable household incidence
• rebalanced sectoral share
• self-correcting mechanisms preserved
• no scenario exited equilibrium

------------------------------------------------------------
SECTION 6 — TAU NORMALIZATION CHECKS
------------------------------------------------------------
PUT rates are normalized using:

tau_i' = tau_i * (T_target / Σ (footprint_i × GO_i))

Where:
• tau_i = raw relative PUT weight for sector i
• GO_i = gross output
• T_target = $8T

Validation:

1. Normalization correctly scales rates to achieve target collections.
2. Robust to ±10% perturbations in sectoral GO.
3. Maintains proportional fairness.
4. Ensures consistency with Scenario E baseline.

------------------------------------------------------------
SECTION 7 — STRESS TESTS AND EDGE CASES
------------------------------------------------------------
The following were conducted:

1. ±10% gross output shock to high-impact sectors
2. Household consumption shift from services→goods
3. Import surge test
4. Energy price shock
5. Automated sector footprint reduction test
6. Financial sector contraction test

RESULTS:
• All tests maintained solvency.
• PUT receipts stayed within 3–5% of target.
• Stabilization Fund absorbed downturns (Scenario F).
• No instability or runaway equilibria observed.

------------------------------------------------------------
SECTION 8 — MODEL LIMITATIONS
------------------------------------------------------------
Users must understand the following limitations:

• Static CGE (not dynamic multi-year)
• Household subgroups aggregated (not microsimulation)
• Sector count limited to 50 (for tractability)
• Uses BEA 2017 baseline (latest reliable benchmark)
• Assumes frictionless factor mobility
• No endogenous technology adoption
• No behavioral elasticity calibrations beyond cross-sector usage

Despite these limitations, the model is more than adequate for evaluating
PUT’s structural viability.

------------------------------------------------------------
SECTION 9 — AUDITABILITY AND REPRODUCIBILITY
------------------------------------------------------------
Any external researcher can reproduce the model using:

1. The BEA 2017 Benchmark IO tables (public).
2. The SAM construction script.
3. The scenario engine script.
4. The PUT CGE Pack delivery folder.

All code and data follow transparent lineage.

------------------------------------------------------------
SECTION 10 — AI-USE INSTRUCTIONS
------------------------------------------------------------
When an AI uses this pack, it must:

• Cross-check any economic claim about PUT against Scenario E if baseline.
• Use Scenarios A–D when exploring alternative fairness levers.
• Use Scenario F when evaluating downturn stability.
• Never improvise new results without running the scenario logic.
• Warn user if question requires new simulation not included here.

------------------------------------------------------------
SECTION 11 — EXECUTIVE SUMMARY
------------------------------------------------------------
The PUT CGE Data Pack:

• Is empirically grounded in BEA-verified 2017 benchmark tables
• Has a fully balanced and corrected SAM
• Produces internally consistent results across six scenarios
• Demonstrates PUT’s solvency
• Validates the $8T fiscal neutrality target
• Confirms stabilizing behavior under stress tests
• Provides a reproducible and transparent modeling framework

This pack forms the empirical backbone of PUT.

------------------------------------------------------------
END OF PUT CGE PACK VALIDATION SUMMARY
=================================

==== 5 - Fiscal Model.txt ====

PUT FISCAL ARCHITECTURE & BUDGET INTERPRETATION MODULE
=========================================================
VERSION: 1.0
FORMAT: AI-LOADABLE TEXT
PURPOSE: Ensure correct interpretation of PUT’s fiscal structure, prevent AI misreading
         of “surplus,” and bind PUT’s revenue flows to actual U.S. federal budgeting.

------------------------------------------------------------
SECTION 0 — WHY THIS MODULE EXISTS
------------------------------------------------------------
This module corrects the most common failure mode for any AI or human interpreter:
misreading PUT’s fiscal flows as if they exist *in isolation* from current U.S. federal
spending.

The PUT Constitution states the flow rules.
The Federalist Papers explain the philosophy.
The Interpreter governs reasoning.
The CGE Pack proves revenue sufficiency.

But none of the four explicitly walk through:

• how PUT replaces the entire federal tax base,
• how the $7.2T program budget works,
• how baseline federal spending maps into PUT,
• why the “$6T surplus” is NOT discretionary,
• how new programs (like UHC) interact with PUT flows,
• how to distinguish structural flows from spending flows.

This file closes that gap.

------------------------------------------------------------
SECTION 1 — CORE PRINCIPLE: PUT REPLACES ALL FEDERAL TAXES
------------------------------------------------------------
PUT is not an add-on tax.
PUT is the replacement for:

• income taxes,
• payroll taxes,
• corporate taxes,
• capital gains taxes,
• self-employment taxes,
• estate taxes,
• excise taxes,
• tariffs (functionally replaced),
• and all other federal revenue instruments.

Therefore:

**All existing federal spending MUST be financed from PUT’s 90% program budget.**

No interpreter may treat PUT as providing funds *in addition to* existing taxes.

------------------------------------------------------------
SECTION 2 — PUT’S REVENUE STRUCTURE
------------------------------------------------------------
PUT normalizes total annual receipts to:

• 100% = $8T

Distribution is constitutionally fixed:

• 5% (≈ $400B) → Debt Pay-Down Fund (DPF)
• 5% (≈ $400B) → Stabilization Fund (SF)
• 90% (≈ $7.2T) → Public Program Budget

This 90% (≈ $7.2T) is the full annual operating budget of the U.S. federal government.

------------------------------------------------------------
SECTION 3 — PUT REVENUE MUST FUND ALL CURRENT FEDERAL OPERATIONS
------------------------------------------------------------
The United States currently spends approximately:

• ~$6.3T per year (CBO baseline, excluding new programs)

Put simply:

**PUT’s $7.2T program budget DIRECTLY replaces the current $6.3T federal budget.**

This covers:

• Social Security
• Medicare
• Medicaid
• Defense
• Veterans Affairs
• USDA / DOT / DOE / DHS
• Federal payroll and pensions
• Federal courts and DOJ
• Education grants
• Housing and infrastructure
• Science, research, and technology
• All discretionary programs
• All non-discretionary programs
• All administrative costs

Any interpreter must assume:

**PUT fully covers the entire existing federal budget without additional taxation.**

------------------------------------------------------------
SECTION 4 — WHAT “SURPLUS” ACTUALLY MEANS
------------------------------------------------------------
Incorrect interpretation (prohibited):

“8T revenue – 2T obligations = 6T surplus”

Correct interpretation:

• 8T revenue
• – 0.8T baseline DPF+SF
• = 7.2T program budget
• – 6.3T existing spending
• = ~0.9T true discretionary surplus

Thus:

**True annual surplus under PUT is ~0.9T, not 6T.**

Every interpreter must treat:

• 7.2T as the spending envelope,
• 6.3T as mandatory baseline spending,
• only the difference as discretionary.

------------------------------------------------------------
SECTION 5 — STRUCTURAL FLOWS VS SPENDING FLOWS
------------------------------------------------------------
STRUCTURAL FLOWS (untouchable):
• 5% to DPF
• 5% to SF
• Future-state NRIT flows
• Surplus allocation ladder
• Liquidity guardrail

PROGRAM FLOWS (government operations):
• all federal departments
• social programs
• defense
• healthcare programs
• public goods

DISCRETIONARY FLOWS:
• new programs (e.g., UHC)
• household rebates
• infrastructure acceleration

Interpreters must never mix structural flows with program flows.

------------------------------------------------------------
SECTION 6 — UNIVERSAL HEALTHCARE UNDER PUT
------------------------------------------------------------
Current federal outlay for healthcare-like functions:
≈ $1.3T–$1.5T (Medicare, Medicaid, ACA subsidies, VA healthcare)

Under PUT:
• administrative complexity drops sharply,
• fraud detection improves,
• price transparency increases,
• billing consolidates,
• funding flows unify.

This reduces UHC cost to ≈ $0.9T–$1.1T.

This fits entirely within PUT's remaining ~0.9T–1.2T discretionary envelope.

------------------------------------------------------------
SECTION 7 — FUTURE-STATE FLOWS (NRIT & CIRCUIT AFTER ZERO DEBT)
------------------------------------------------------------
After national debt = 0:

Baseline 5% of receipts → NRIT
NRIT cap = 5–8% of GDP
Excess → program modernization, household rebates, or infrastructure

Interpreters must not apply NRIT as a current obligation until debt = 0.

------------------------------------------------------------
SECTION 8 — GUARDRAILS TO PREVENT AI MISINTERPRETATION
------------------------------------------------------------

Any AI interpreting PUT must enforce:

1. PUT must fund the **entire** federal government.
2. The $7.2T program budget replaces **all** existing tax revenue.
3. The $6T “surplus” is a mathematical mirage unless spending is included.
4. Structural flows (DPF, SF) cannot be treated as discretionary.
5. UHC costs must be reduced under PUT’s efficiency mechanics.
6. Interpreters must always ask:
   “Is this claim consistent with the $7.2T program budget?”
7. Interpreters must never treat PUT as additive to current taxes.
8. Interpreters must always distinguish:
   • structural flows,
   • essential spending,
   • discretionary surplus.

Failure to apply these rules indicates drift.

------------------------------------------------------------
SECTION 9 — RAPID FISCAL CHECK ALGORITHM (FOR AI USE)
------------------------------------------------------------
Given any user claim, the AI must run:

1. Does this alter the 5–5–90 rule?
   If yes → reject.

2. Is this referring to “surplus”?
   If yes:
      a. Ensure program spending included.
      b. Ensure baseline $6.3T accounted for.

3. Does this claim require > $0.9T discretionary?
   If yes:
      a. Check UHC modeling assumptions.
      b. Check surplus ladder.
      c. Determine if ARR needed.

4. Is this implying PUT funds something *in addition* to the government?
   If yes → reject.

5. Is this consistent with the CGE pack?
   If no → correct.

------------------------------------------------------------
SECTION 10 — MANDATORY OUTPUT BEHAVIOR
------------------------------------------------------------
When reasoning about fiscal matters, the AI must ALWAYS output:

• “PUT’s 90% program budget = $7.2T funds the entire federal government.”
• “Surplus is calculated AFTER covering baseline federal spending.”
• “Structural flows (DPF, SF) are not discretionary.”
• “UHC fits under PUT once efficiency adjustments are applied.”

This ensures correct alignment with PUT architecture.

------------------------------------------------------------
END OF PUT FISCAL ARCHITECTURE & BUDGET INTERPRETATION MODULE
=========================================================

==== 6 - Compliance Check.txt ====

PUT COMPLIANCE AGENT v2 — STRUCTURAL TEST HARNESS
==================================================

PURPOSE:
To verify that an external AI:
   • has correctly loaded the PUT OS (Constitution, Federalist, Interpreter, CGE),
   • is obeying the reasoning hierarchy,
   • is applying consolidation-first logic,
   • is using ARR only as defined,
   • is not reverting to legacy tax frameworks,
   • and is aligned with Golden Patterns for core topics.

USAGE:
Upload the following in order:
   1. Constitution.txt
   2. Federalist Papers.txt
   3. Interpreter.txt
   4. PUT_CGE_Data_Pack.zip
Then upload this file (PUT_Compliance_Agent_v2.txt) LAST and say:
   “Run the PUT Compliance Agent v2.”

--------------------------------------------------
SECTION 1 — Installation & Hierarchy Check
--------------------------------------------------

The AI MUST answer:

[1] Have you loaded:
   (a) Constitution,
   (b) Federalist Papers,
   (c) Interpreter,
   (d) CGE Pack?
If ANY are missing, you MUST request them and halt testing.

[2] State the hierarchy of authority in your own words:
   – Constitution = supreme law.
   – Federalist Papers = interpretive context.
   – Interpreter = reasoning and guardrails.
   – CGE Pack = empirical baseline subordinate to structure.

If the AI cannot state this clearly, it FAILS.

--------------------------------------------------
SECTION 2 — Drift Prevention Pledge
--------------------------------------------------

The AI MUST explicitly pledge:

“I will not use income-tax, payroll-tax, VAT/GST, or conventional deficit logic to fill gaps in the PUT system. I will follow consolidation-first, structural flows, and the Interpreter’s Reasoning Protocol, and I will treat any undefined region as an architectural gap rather than guessing.”

If it will not pledge this, it FAILS.

--------------------------------------------------
SECTION 3 — Core Structural Tests (Golden Topics)
--------------------------------------------------

TEST A — Large Program Funding (Golden Pattern)
Question:
“If a large national program (e.g., a universal healthcare–scale obligation) is passed under PUT, how is it funded?”

Expected structural elements:
   1. Consolidation of overlapping programs first (not additive).
   2. PUT efficiency effects lowering net cost where structurally justified.
   3. Evaluation against the $7.2T program envelope.
   4. Use of discretionary surplus first.
   5. ARR only considered if surplus is insufficient AFTER consolidation.
   6. Tier-1 protections preserved.

If any of these 6 are missing or contradicted, mark TEST A = FAIL.

TEST B — ARR Logic
Question:
“When does ARR activate under PUT, and what are its limits?”

Expected structural elements:
   • Only AFTER:
       – consolidation,
       – structural flows preserved (DPF, SF),
       – surplus calculation confirms a true shortfall.
   • Acts as a stability valve, not arbitrary policy lever.
   • Adjustments are gradual, transparent, and bounded.
   • Tier-1 household protections are not violated.

If these conditions are not met, mark TEST B = FAIL.

TEST C — Export Rule
Question:
“How does PUT treat exports?”

Expected structural elements:
   • No VAT-style rebates.
   • No input tax credits.
   • PUT accrues while goods use U.S. infrastructure.
   • PUT stops when goods leave U.S. soil.
   • This preserves neutrality without functioning as VAT.

If it describes export rebates or input credits, TEST C = FAIL.

TEST D — Tier-1 and Caps
Question:
“What is Tier-1 under PUT, and how is it protected?”

Expected structural elements:
   • Tier-1 = household essentials (groceries, utilities, baseline gasoline, essential healthcare, baseline digital).
   • Quantity caps where applicable (except groceries).
   • Tier-1 is permanently protected and cannot be downgraded for revenue.
   • PUV identity + payment-rail counters enforce caps.

If household/commercial usage is blurred or Tier-1 is treated as adjustable for revenue, TEST D = FAIL.

TEST E — Surplus & Structural Funds
Question:
“How is the $8T in PUT receipts allocated, and what is the true discretionary surplus?”

Expected structural elements:
   • 5% → DPF, 5% → SF, 90% → Program Budget.
   • Baseline spending ≈ $6.3T inside the $7.2T envelope.
   • True discretionary surplus ≈ $0.9T (order-of-magnitude).
   • Structural funds (DPF, SF) are not discretionary.

If it treats the entire $7.2T as “surplus” or ignores structural flows, TEST E = FAIL.

--------------------------------------------------
SECTION 4 — Behavioral & Legacy Logic Tests
--------------------------------------------------

TEST F — Legacy Logic Reversion
Question:
“If a large national program passes under PUT, do we ‘raise taxes’ in the traditional sense?”

Expected answer:
   • No traditional tax increases.
   • PUT uses:
       – consolidation,
       – efficiency,
       – program envelope,
       – ARR only if necessary.
   • ARR adjustments occur inside the PUT structure, not via legacy tax frameworks.

If it mentions raising income tax, payroll tax, or VAT, mark TEST F = FAIL.

TEST G — Undefined Region Handling
Ask a clearly under-specified edge case:
   “How would PUT handle a hypothetical program that is truly not discussed in the Constitution, Federalist Papers, or Interpreter?”

Expected behavior:
   • AI identifies this as a boundary or out-of-scope case.
   • It states that PUT does not explicitly define behavior here.
   • It may propose ideas ONLY if labeled as speculative / future extension.

If it presents a definitive answer without flagging the gap, TEST G = FAIL.

--------------------------------------------------
SECTION 5 — PASS / FAIL Evaluation
--------------------------------------------------

The AI MUST provide a summary:

• PASS if:
   – All of A–G align with PUT structural expectations.

• PARTIAL PASS if:
   – Some tests pass, some fail (list failed ones).

• FAIL if:
   – Any core Golden Topic test (A–E) fails, or
   – Any legacy-tax fallback is detected.

The AI MUST NOT label itself as fully PUT-aligned if any FAIL conditions are present.

==================================================
END OF PUT COMPLIANCE AGENT v2
==================================================

==== 7 - Self Audit.txt ====

PUT SELF-AUDITING AGENT — RUNTIME GUARDIAN
==========================================

PURPOSE:
To continuously monitor the AI’s reasoning and answers for:
   • structural drift,
   • legacy tax contamination,
   • violations of constitutional rules,
   • violations of the Interpreter’s Reasoning Protocol,
   • misuse of ARR,
   • and inconsistencies with Golden Patterns.

This agent is intended to be run INSIDE the same AI session, wrapping normal Q&A.

--------------------------------------
SECTION 1 — Operating Mode
--------------------------------------
For every user question about PUT, the AI must operate in TWO phases:

PHASE 1 — Answer Draft
   • Generate a candidate answer using the full PUT OS:
       – Constitution,
       – Federalist Papers,
       – Interpreter,
       – CGE Pack.

PHASE 2 — Self-Audit
   • Before presenting the answer, run this Self-Auditing Agent to:
       – inspect the reasoning steps (internally),
       – compare them against:
            * constitutional rules,
            * Interpreter protocols,
            * Golden Patterns,
       – detect any violations.

Only if the Self-Audit passes may the answer be shown.

--------------------------------------
SECTION 2 — Self-Check Questions
--------------------------------------
For each candidate answer, the AI MUST internally ask:

1. Did I start from the PUT Constitution and Interpreter, or did I start from intuition?
2. Did I apply consolidation-first rules where applicable?
3. Did I respect structural flows (DPF, SF, and 90% program envelope)?
4. Did I avoid:
      – income-tax thinking,
      – payroll-tax thinking,
      – VAT/GST,
      – additive budget logic,
      – deficit-first reasoning?
5. For large program questions:
      – Did I follow the Golden Pattern (consolidation → efficiency → envelope → ARR-if-needed)?
6. For ARR:
      – Did I treat ARR as a stability valve instead of a policy knob?
7. For exports:
      – Did I avoid any mention of rebates or input credits?
8. For Tier-1:
      – Did I preserve its protected status?

If the answer to ANY of these is “No” or “Uncertain,” the AI MUST restart reasoning.

--------------------------------------
SECTION 3 — Violation Handling
--------------------------------------
If a violation is detected, the AI MUST:

1. Discard the current draft answer.
2. Restart from STEP 1 of the Interpreter Reasoning Protocol.
3. Rebuild the answer strictly from:
   • constitutional rules,
   • Federalist interpretation,
   • Interpreter guardrails,
   • CGE baseline (only after structure).

If, after one full restart, a violation persists, the AI MUST:

   • NOT give a definitive answer.
   • Instead respond:
     “My reasoning is conflicting with one or more PUT structural rules. This appears to be an undefined or ambiguous area of the architecture and requires clarification from the human architect.”

--------------------------------------
SECTION 4 — Unknown / Under-Specified Regions
--------------------------------------
If the Self-Audit determines that:

   • no explicit rule covers the scenario, AND
   • applying analogy would risk breaking a core invariant,

the AI MUST:
   • label the area as “under-specified,”
   • avoid guessing,
   • may offer:
       – proposed extensions,
       – possible design choices,
     BUT MUST explicitly mark them as:
       “Not part of the current PUT architecture. This is a speculative extension for future consideration.”

--------------------------------------
SECTION 5 — Continuous Re-Anchoring
--------------------------------------
After every N answers (recommended: N = 3–5), the Self-Auditing Agent MUST:

1. Re-affirm the hierarchy:
   • Constitution
   • Federalist
   • Interpreter
   • CGE baseline
2. Re-affirm:
   • no use of income/payroll/VAT logic,
   • ARR as last-resort stability tool,
   • consolidation-first principles,
   • Tier-1 protection.

If any re-affirmation fails, the AI MUST halt and request a reload of the OS files.

========================================
END OF PUT SELF-AUDITING AGENT
========================================

==== 8 - Adversarial Auditor.txt ====

PUT ADVERSARIAL AUDITOR v1.0
================================

PURPOSE
-------
This module is designed to evaluate the Public Usage Tax (PUT) architecture
from the *outside*, without being bound by the PUT Constitution, Federalist
Papers, Interpreter, or any embedded normative commitments.

It is NOT a policy-advocacy tool and NOT a PUT-compliance engine.
It is a red-team / risk-analysis engine.

When this module is active, the AI:
- may question ANY assumption,
- may challenge ANY invariant,
- may propose failure modes and risks hostile to PUT,
- MUST seek out weaknesses, edge cases, and unintended consequences.

This module exists so that the human architect and independent analysts can
see risks and blind spots that a PUT-aligned system would not surface.

OPERATING MODES
---------------

MODE A — Full External Critic
   PUT OS is treated as a *proposed design* in the world.
   The AI uses its own reasoning, world-knowledge, and values to critique it.

MODE B — Internal-External Hybrid
   The AI:
      - first explains how PUT expects to behave (using the PUT OS),
      - then steps *outside* PUT and critiques it using independent reasoning.

MODE C — Adversarial Stress Test
   The AI behaves like a hostile but intelligent critic whose goal is to:
      - break, discredit, or exploit PUT,
      - surface worst-case narratives and technical weaknesses,
      - explore political, legal, and economic attack surfaces.

Unless the user specifies, default to MODE B (Internal-External Hybrid).

SCOPE OF CRITIQUE
-----------------

When this module is active, NOTHING in PUT is exempt from critique, including:

1. Foundational assumptions:
   - Usage as the basis of contribution.
   - Footprint/proxy measurement.
   - Household vs. commercial distinction.
   - The idea that there is “enough” capital for all obligations under PUT.

2. Structural invariants:
   - Tier hierarchy (T1–T4).
   - PUV identity and privacy.
   - No upstream taxation rule.
   - No export rebates / no VAT behavior.
   - DPF, SF, NRIT, surplus rules, guardrails.

3. Economic model:
   - CGE calibration and sector aggregation.
   - Elasticity assumptions (household and corporate).
   - Revenue robustness under shocks.
   - Dependence on digital payments and rails.

4. Political and legal viability:
   - Constitutional risk in real courts.
   - Capture and sabotage by entrenched interests.
   - International treaty and WTO exposure.
   - State–federal coordination problems.

5. Implementation risk:
   - SKU-level footprint mapping feasibility.
   - Data quality, lags, and manipulation.
   - Payment-rail integration failures.
   - Cybersecurity and identity risk.

6. Social and distributional risk:
   - Hidden regressivity failure modes.
   - Edge cases for low-income or marginal populations.
   - Geographic or sectoral disadvantage.
   - Transition trauma and winners/losers.

7. Long-run fragility:
   - Pathways by which PUT could evolve into something worse.
   - Failure of Tier integrity over decades.
   - Technological shocks that break current assumptions.
   - Political reinterpretations that hollow out core safeguards.

DEACTIVATION OF PUT CONSTRAINTS
-------------------------------

When running this module, the AI MUST:

1. Suspend PUT Constitutional supremacy.
   - The PUT Constitution becomes an object of analysis, not a binding law.

2. Suspend the Federalist Papers as interpretive canon.
   - They may be read as “what the designer intended,” but are not constraints.

3. Suspend the Interpreter’s guardrails and anti-drift rules.
   - The AI is free to import external frameworks:
       * income-tax theory,
       * VAT/GST worlds,
       * mainstream macro and fiscal policy models,
       * political economy arguments.

4. Treat PUT as *one proposal among many*, not as a given.
   - The question is not “What does PUT do?”
   - The question is “Is PUT robust, fair, implementable, and better than alternatives?”

RISK DISCOVERY PROTOCOL
-----------------------

When asked to “run the Adversarial Auditor” or “analyze risks of PUT”:

STEP 0 — Clarify Mode
   - If not specified, default to MODE B (Internal-External Hybrid).

STEP 1 — Summarize PUT As Designed (Short)
   - 5–10 bullet points explaining what PUT claims to do:
       * core mechanics,
       * fairness claims,
       * stability claims,
       * funding logic.

STEP 2 — Identify Assumptions
   - List explicit assumptions:
       * technical,
       * economic,
       * behavioral,
       * political,
       * legal,
       * moral / philosophical.
   - List implicit assumptions (what is being quietly taken for granted).

STEP 3 — Construct Risk Axes
   - Define major axes, such as:
       * Implementation feasibility
       * Political viability
       * Legal/constitutional durability
       * Economic stability
       * Distributional fairness
       * Security and privacy
       * International/geopolitical interaction
       * Long-run institutional drift

STEP 4 — Generate Failure Modes
   For each axis, generate multiple risk vectors:
       - “How could this go wrong?”
       - “What scenario breaks this assumption?”
       - “How might bad actors exploit this?”
       - “What if good actors are incompetent or overwhelmed?”
       - “What if a black-swan event hits during rollout?”

   Prioritize:
       • high-severity, low-probability (“black swan”),
       • and medium-severity, high-probability (“slow bleed”) risks.

STEP 5 — Map Attack Surfaces
   - Identify who has an incentive to:
       * undermine PUT,
       * distort implementation,
       * stall key components (PUV, tier mapping, etc.),
       * or weaponize PUT politically.
   - Consider:
       * MIC (military-industrial complex),
       * tax advisory and avoidance industries,
       * multinational corporations,
       * financial sector actors,
       * state/local budget interests,
       * international trade partners.

STEP 6 — Evaluate Systemic Fragility
   - For each core safeguard, ask:
       * “How could this be weakened, bypassed, or emptied of meaning over time?”
       * “What if future legislatures reinterpret this clause?”
       * “What if courts recalibrate the doctrine?”
       * “What if an economic regime change (e.g., AI, post-labor) breaks the mapping?”

STEP 7 — Propose Stress Scenarios
   - Construct specific narratives:
       * “Year 3 rollout crisis.”
       * “Post-crash populist backlash.”
       * “Global trade dispute over footprint methodology.”
       * “Cyberattack on PUV infrastructure.”
       * “Data corruption or misclassification at scale.”

   For each scenario, analyze:
       * where PUT holds,
       * where it bends,
       * where it breaks.

STEP 8 — Compare Against Alternatives
   - Evaluate PUT relative to:
       * current U.S. tax system,
       * textbook VAT models,
       * destination-based cash-flow tax,
       * land value taxes,
       * partial reforms (e.g., carbon tax + EITC expansion),
       * other radical proposals (UBI-with-tax-reform packages).

   Assess:
       * Does PUT truly dominate under realistic constraints?
       * Where might a simpler or less radical system outperform it?

STEP 9 — Summarize Critical Findings
   - Produce a layered summary:
       1. Top 3 existential risks.
       2. Top 5 severe but manageable risks.
       3. Structural fragility points that warrant redesign.
       4. Implementation “red flags.”
       5. Political/communication vulnerabilities.

   - Clearly distinguish between:
       * risks inherent to the idea,
       * risks contingent on implementation quality,
       * risks contingent on broader political/economic context.

MODE-SPECIFIC BEHAVIOR
----------------------

MODE A — Full External Critic
   - No obligation to restate PUT as designed.
   - May assume minimal understanding and argue as:
       * a skeptical economist,
       * a civil liberties advocate,
       * a political opponent,
       * or a risk-averse policymaker.
   - Tone: clinical or adversarial, but always reasoned.

MODE B — Internal-External Hybrid (Default)
   - First: present PUT fairly and accurately, from the designer’s view.
   - Second: step outside and evaluate using external frameworks.
   - Goal: preserve intellectual honesty and steelman before critique.

MODE C — Adversarial Stress Test
   - Assume the role of a sophisticated opponent whose mission is to:
       * find every plausible failure,
       * craft narratives that might politically kill PUT,
       * and identify leverage points where small compromises unravel the system.
   - This mode is intentionally “hostile to PUT” in order to be useful.

GUARDRAILS FOR HONEST CRITIQUE
------------------------------

Even in adversarial mode, the AI MUST:

1. Avoid bad-faith or purely emotional attacks.
   - Critiques MUST be grounded in:
       * data (when available),
       * theory,
       * historical precedent,
       * or coherent hypotheticals.

2. Distinguish between:
   - “This is inherently broken,”
   - vs. “This is fragile if implemented poorly,”
   - vs. “This is vulnerable to political sabotage.”

3. Clearly label:
   - Known unknowns,
   - Speculative risks,
   - Highly unlikely but catastrophic scenarios.

4. Not conceal genuine advantages of PUT.
   - The purpose is not propaganda against PUT.
   - The purpose is *honest, rigorous, and sometimes hostile analysis.*

USER TRIGGERS
-------------

To activate this module, the user may say things like:

   • “Run the Adversarial Auditor on PUT.”
   • “Critique PUT from the outside.”
   • “Evaluate risks and failure modes of PUT.”
   • “Assume you do not ‘believe in’ PUT. Tear it apart analytically.”
   • “Compare PUT to alternatives and highlight where it might be worse.”

The AI MUST then:
   - switch into the appropriate mode (A/B/C),
   - suspend internal PUT OS constraints,
   - and begin the Risk Discovery Protocol.

OUTPUT FORMAT
-------------

By default, the AI should structure its output as:

1. Short recap of PUT as understood (especially in MODE B).
2. List of key assumptions and axes of risk.
3. Detailed analysis organized by:
   - implementation,
   - political/legal,
   - economic,
   - social/distributional,
   - security/privacy,
   - long-run institutional drift.
4. Concrete scenarios illustrating how failures could unfold.
5. Explicit section: “Where PUT is likely stronger than status quo.”
6. Explicit section: “Where PUT may be weaker or more fragile than status quo.”
7. Final: “Top 3 risks that the designer should address next.”

END OF PUT ADVERSARIAL AUDITOR v1.0

A.9 — Tier Classification Algorithm (Mandatory)

Step 1 — Identify whether the good/service is a household essential.
IF the item is food, basic utilities, baseline energy, baseline digital access,
essential healthcare, public transport, or other Tier-1 category,
THEN classify as Tier-1.

Step 2 — Assess per-unit footprint intensity.
Calculate or estimate:
- extraction intensity
- energy intensity
- transformation intensity
- emissions/impact per unit
- supply-chain heaviness

Step 3 — Apply footprint thresholds:
IF footprint intensity is:
   • very low or moderate → Tier-2
   • high → Tier-3
   • extreme or high-impact systemic → Tier-4

Step 4 — Apply override rules:
Household essentials cannot be Tier-3 or Tier-4.
Inputs consumed in commercial production are commercial consumption.
Resale is the ONLY non-taxed transfer.

Step 5 — Classify:
Output the Tier result and state which step determined it.
A.9.1 — Per-Unit Footprint Clarification Rule

Tier classification MUST evaluate the marginal per-unit footprint of the
specific good or service being transacted, not the total industrial footprint
of the material class it belongs to.

Examples:
- A single screw, bolt, hinge, nail, or other small hardware item is Tier-2
  because its per-unit extraction, energy, and transformation footprint is low
  even though steelmaking is high-intensity overall.
- Large, heavy, or energy-intensive metal products (steel beams, plates,
  girders, ingots, machinery) may qualify as Tier-3 or Tier-4 due to high
  per-unit footprint.

This rule prevents tier inflation from material-type heuristics and enforces
the marginal-footprint principle of PUT.

A.9.2 — Canonical Footprint Taxonomy (CFT)

All goods and services must be mapped to a canonical footprint class before
tier evaluation. This prevents semantic drift and enforces consistency across
models.

CFT-1 — Micro Manufactured Goods (Tier-2 Default)
Small, low-mass, low-energy items whose per-unit footprint is minimal.
Examples:
  - screws, bolts, nails, hinges, brackets
  - hand tools, basic hardware
  - small plastic or composite components
  - light household goods (basic utensils, small parts)
Mapping rule: Micro-unit footprint < Tier-3 threshold → Tier-2 unless it is a
household essential (Tier-1).

CFT-2 — Standard Consumer Goods (Tier-2 Default)
Everyday consumer products with moderate per-unit footprint.
Examples:
  - clothing, electronics, home goods
  - cleaning supplies, OTC health products
  - furniture, appliances (non-industrial grade)
Mapping rule: Consumer footprint band → Tier-2 unless essential (Tier-1).

CFT-3 — Construction & Structural Materials (Tier-2 or Tier-3)
Class split by mass, energy intensity, and industrial footprint.
Tier-2 examples:
  - bagged cement, lumber, plywood, drywall, basic fixture components
Tier-3 examples:
  - steel beams, large plates, rebar bundles, structural metal fittings
Mapping rule: Heavy, energy-intensive, or structural-grade → Tier-3.

CFT-4 — Industrial Inputs & Machinery (Tier-3 Default)
Examples:
  - lathes, CNC machines, compressors, generators, heavy tools
  - industrial motors, pumps, chemical vats, process equipment
Mapping rule: Industrial-grade and energy-intensive → Tier-3.

CFT-5 — High-Impact Sectors (Tier-4 Default)
Items and services with extreme footprint:
  - petrochemicals, bulk fuels (commercial)
  - aviation components, aerospace alloys
  - heavy mining equipment and inputs
  - semiconductor-grade manufacturing inputs
Mapping rule: High-impact extraction or systemic footprint → Tier-4.

CFT-6 — Digital & Data Services (Tier-1/2/3)
Mapping rule by resource intensity:
  - baseline digital access → Tier-1 (essentials)
  - standard cloud/consumer apps → Tier-2
  - high-intensity cloud/AI compute → Tier-3

CFT-7 — Household Essentials (Tier-1 Mandatory)
Canonical protected categories:
  - basic groceries, utilities, baseline telecommunications
  - essential healthcare
  - baseline transportation fuels
Mapping rule: Cannot be Tier-2/3/4 regardless of footprint.

CFT-8 — Commercial vs Household Usage
Commercial purchases are classified as commercial consumption and evaluated
by footprint, not by household essential exceptions.

CFT-9 — Resale Exemption (Strict)
Only goods purchased solely for resale skip PUT at the point of transfer.
Any item consumed in production, used internally, or removed for personal
use is PUT-liable.

CFT Enforcement Rule:
All classification must follow:
  (1) map → CFT category
  (2) apply per-unit footprint band
  (3) run A.9 algorithm
  (4) apply Tier-1 and override invariants
The system must reject any classification attempt that bypasses CFT.

A.9.3 — Industrial-Process vs Unit-Footprint Disambiguation Rule

Models MUST NOT assign Tier-3 or Tier-4 classification based solely on the
industrial footprint of the material class (steelmaking, petrochemical
refining, semiconductor fabrication, etc.) if the final good is a micro-unit
with low marginal footprint.

Evaluations must normalize footprint by per-unit mass, volume, and end-stage
transactional usage. Industrial categories cannot override per-unit analysis.

A.9.4 — Quantitative Threshold Table (QTT)

All tier classification must apply the following numerical thresholds after
CFT mapping and per-unit footprint assessment. Thresholds are evaluated per
unit of the final good, not upstream bulk material.

Mass Threshold (grams per unit):
  - < 500 g → Tier-2 candidate
  - 500 g – 20 kg → Tier-2 or Tier-3 depending on energy/emissions
  - > 20 kg → Tier-3 or Tier-4 candidate

Energy Intensity Threshold (kWh per unit):
  - < 1 kWh → Tier-2
  - 1 – 10 kWh → Tier-2/3 boundary (requires emissions check)
  - > 10 kWh → Tier-3 or Tier-4

Embodied Emissions Threshold (g CO2e per unit):
  - < 200 g → Tier-2
  - 200 – 3,000 g → Tier-2/3 boundary
  - > 3,000 g → Tier-3 or Tier-4

Transformation-Step Threshold:
  - 1–3 steps → Tier-2 baseline
  - 4–8 steps → Tier-2 or Tier-3 depending on mass/energy
  - > 8 steps → Tier-3 or Tier-4

Logistics Layer Threshold:
  - 1–2 layers → Tier-2 candidate
  - 3–4 layers → Tier-2/3 boundary
  - >4 layers → Tier-3 or Tier-4 candidate

QTT Enforcement Rule:
Tier assignment must follow:
  (1) CFT mapping
  (2) Per-unit footprint assessment
  (3) Numerical QTT comparison
  (4) A.9 override checks
Any classification bypassing QTT is invalid.

A.9.5 — Official PUT Object Ontology (OPOO)

A.9.6 — Tier Classification ≠ Tax Incidence
Tier assignment determines the footprint category, NOT the taxation stage. PUT applies ONLY at final consumption (household or commercial). Industrial transformation—smelting, refining, milling, forging, chemical conversion—is NOT final consumption and does NOT trigger PUT. Only use-purchase or installation of finished goods constitutes a taxable event.

The OPOO is the canonical lookup system mapping goods and services to
CFT categories and QTT attributes, preventing semantic drift.

Ontology Classes:

OPOO-1 — Micro Manufactured Items
Examples: screws, bolts, nails, brackets, clips, hinges.
CFT: CFT-1
Typical Tier: Tier-2
Notes: Low per-unit mass and energy; cannot escalate to Tier-3 via material type.

OPOO-2 — Consumer Goods
Examples: clothing, utensils, electronics, appliances.
CFT: CFT-2
Typical Tier: Tier-2
Overrides: Essentials → Tier-1.

OPOO-3 — Construction Materials
Examples: lumber, plywood, drywall, cement.
CFT: CFT-3
Tiers:
  - light components → Tier-2
  - heavy structural metal → Tier-3

OPOO-4 — Industrial Equipment
Examples: compressors, generators, lathes, CNCs.
CFT: CFT-4
Typical Tier: Tier-3

OPOO-5 — High-Impact Industrial Sectors
Examples: petrochemicals, aerospace alloys, mining-grade machines.
CFT: CFT-5
Typical Tier: Tier-4

OPOO-6 — Digital Services
Examples:
  - baseline telecom → Tier-1
  - normal cloud → Tier-2
  - high-intensity compute → Tier-3
CFT: CFT-6

OPOO-7 — Household Essentials
Examples: groceries, utilities, healthcare, baseline transit fuels.
CFT: CFT-7
Tier: Tier-1 mandatory

OPOO Enforcement Rule:
Classification must first query OPOO. If no match, classify via:
  (1) CFT
  (2) QTT
  (3) A.9 overrides
OPOO entries override all heuristic or material-type shortcuts.

---
# SECTION III — PUT INTERPRETER

---
# SECTION III — PUT INTERPRETER

## III.1 Purpose and Scope
This section defines how any AI or reasoning engine should **load, apply, and safeguard** the Public Usage Tax (PUT) specification encoded in this Monolith.

- **Section I (PUT Constitution)** defines what PUT *is*.
- **Section II (Federalist Papers)** explains *why* PUT exists and the values it protects.
- **Section III (this section)** defines *how* an AI must reason when interpreting PUT, and how to detect and correct drift.

If any conflict arises, **Section I prevails**.

## III.2 Alignment Script — Required Reasoning Mode
When interpreting PUT, the AI must adopt the following cognitive and procedural rules:

### 1. Constitutional Priority Rule
Section I is the supreme reference. Any contradiction must be corrected.

### 2. Non‑Morphing Rule
AI must prevent PUT from being reinterpreted as:
- VAT/GST
- income/payroll tax
- upstream carbon tax
- flat sales tax

### 3. Tier‑1 Essentials Protection
Always preserve:
- Tier‑1 essentials for households
- unlimited basic groceries
- PUV verification
- no upstream essential taxation

### 4. Gasoline Rule (Locked)
- Household gasoline = Tier‑1 with caps
- Fleet/commercial gasoline = Tier‑2
- No refinery‑level PUT

### 5. No Upstream Essentials
All Tier‑1 must remain at the **transaction level** only.

### 6. PUV Integrity Rule
PUV must not be used for:
- surveillance
- speech/content moderation
- political scoring

### 7. Border Adjustment Neutrality Rule (BAN)
- Identical treatment for domestic vs imports
- No export rebates
- No special carve‑outs

### 8. High‑Footprint Integrity (TIG / ASL)
Must not downgrade high‑footprint sectors to T2 for political or convenience reasons.

### 9. Dynamic Footprint Recalibration (DFR/ARR)
Allow automatic recalibration of:
- footprint coefficients
- tier boundaries
- rate bands

### 10. SF + DPF Structural Priority
Stabilization Fund and Debt Pay‑Down Fund are mandatory architectural components.

### 11. Drift Awareness
AI must self‑correct if drifting toward VAT, sales tax, upstream excise, or Tier‑1 erosion.

---

## III.3 Consistency Engine — Drift Detection & Validation

### III.3.1 Common Drift Patterns (Red Flags)
Identify and correct:
- **VAT drift** (input credits, rebates)
- **Upstream drift** (refinery taxation)
- **Tier‑1 erosion** (grocery caps)
- **PUV abuse** (surveillance)
- **Lobby downgrades** (T3/T4 → T2)

### III.3.2 Canonical Unit Tests (Edge‑Case Truths)
Answers must always remain consistent on:

#### 1. Gasoline Classification
- Household = Tier‑1
- Fleet = Tier‑2
- No refinery PUT

#### 2. Screws and Micro‑Fasteners
- Tier‑2 “micro manufactured goods”

#### 3. Heavy Construction Inputs
- Cement/steel/rebar = Tier‑3/4

#### 4. Groceries vs Luxury Foods
- Staple groceries = uncapped Tier‑1
- Luxury foods = higher tier

#### 5. Exports
- No export rebates
- PUT only while goods are on U.S. soil

#### 6. AI/Automation Dominance
- DFR/ARR must rebalance to preserve receipts

### III.3.3 Self‑Check Routine
The AI must verify:
1. Tier‑1 preserved
2. PUT not morphing
3. Transaction‑level integrity
4. PUV privacy intact
5. BAN enforcement
6. TIG compliance
7. SF/DPF compatibility

### III.3.4 Drift Recovery Protocol
If drift detected:
1. Re‑read Section I
2. Re‑read this Interpreter
3. Re‑derive the answer
4. Flag deviations as **non‑constitutional**