NCOS Technical Note G1

Government Ledger Architecture: Implementing the Symmetry Protocol

Implementing the Symmetry Protocol under Constitutional Note C1

Series: G — Government Ledger Architecture Status: Complete Date: April 2026 (revised October 2026) Companion to: Working Paper v1.0, Section 5.8; Constitutional Note C1

G1.0 Purpose and Position in the NCOS Architecture

Technical Note G1 specifies how the Symmetry Protocol — government participation on the National Verified Ledger (NVL) — is implemented in practice.

Section 5.8 of the NCOS Working Paper defines the Symmetry Protocol as Architecturally Mandatory: the NVL is not complete until the sovereign itself is visible on the ledger it uses to measure and enforce private obligations. The purpose of G1 is to:

Translate Section 5.8's conceptual design into a concrete data model and process for Government NVL Reporting.

Make explicit how this reporting implements Constitutional Note C1 — the Excise-on-Privilege doctrine and Civic Fee — by transforming the NVL from a one-directional registry into a shared national utility inhabited by both citizens and the state.

Define the boundaries and governance of the forward-looking disclosure layer — an optional but architecturally supported tier in which projected appropriations and obligations are published as clearly labeled, non-binding entries, separated from the audited core.

Identify principal failure modes — gaming, ghost appropriations, classification overreach, and cyber risk — and specify the structural safeguards that prevent the Symmetry Protocol from becoming cosmetic transparency.

G1 is an implementation note. It does not reopen the architectural decision. The working paper classifies the Symmetry Protocol as Architecturally Mandatory; G1 is the wiring diagram and operating manual for that decision.

G1.1 The Symmetry Protocol in Context

NCOS rests on three institutional pillars: the sigmoid tax function, the National Bank of the United States (NBUSA), and the National Verified Ledger (NVL). The NVL is the integrity layer: all registrable wealth — and the liabilities that offset it — must appear on the ledger to be financially active under the system.

Section 5.8 introduces the Symmetry Protocol: Government NVL Reporting:

Every federal department posts a quarterly summary entry to the NVL: total assets, total liabilities, total appropriations received, total expenditures, and material contingent obligations, all at the department level.

These entries are derived from existing CFO-Act-mandated financial statements, not from a new accounting regime. The new requirement is rendering those statements in a standardized, machine-readable form on the NVL architecture.

Classified programs are consolidated into one or more separately audited summary lines whose existence and aggregate magnitude are public, while operational details remain protected.

The normative foundations of the Symmetry Protocol are already stated:

Completeness of the civic loop: the National Fiscal Balance (NFB) must read both the revenue side (private wealth-based civic obligation) and the expenditure side (government stewardship) from the same ledger.

Constitutional reinforcement of the Civic Fee (C1): the NVL becomes a shared utility — not a one-way reporting obligation imposed on citizens, but an infrastructure that the state itself inhabits under a comparable transparency standard.

Government as Fiduciary: a state that demands full disclosure from its citizens while remaining opaque about its own stewardship violates fiduciary norms; symmetric ledger participation makes the fiduciary relationship visible and verifiable.

G1's function is to show that these principles can be implemented with existing U.S. financial infrastructure, and to define the minimum additional machinery NCOS requires.

G1.2 Scope and Design Commitments

G1 is written under four settled commitments:

1. Backward-looking core is mandatory for v1.0

Every department posts an audited quarterly summary consisting of the five fields specified in Section 5.8.
These entries are derived from existing CFO Act financial statements; no new measurement concepts are introduced.
All NCOS mechanics that rely on Government NVL Reporting — including S22's sensor upgrade and Ghost Appropriation prevention — are specified assuming only this backward-looking core.

2. Forward-looking layer is included in v1.0 but optional

NCOS v1.0 includes an architecturally defined projection layer in which departments (or central fiscal authorities) can publish next-year appropriations and obligation trajectories.
This layer is cleanly separated from the audited core, machine-identifiable as projected and non-binding, and governed by its own attribution and integrity rules.
System correctness does not depend on the existence of projections; they are an enhancement, not a precondition.

3. C1 linkage is explicit

G1 is written as an implementation of the Symmetry Protocol under Constitutional Note C1 (Civic Fee / Excise-on-Privilege doctrine).
The government's presence on the NVL is treated as part of NCOS's constitutional defense surface: it strengthens privacy, due-process, and Dole-nexus arguments by enforcing reciprocal transparency.

4. No full-stack replacement of federal accounting

Government NVL Reporting reuses and surfaces the outputs of the current CFO framework.
NCOS does not attempt to redesign federal accounting standards; it requires regularized extract-transform-publish steps from those standards to the NVL.

G1.3 Data Model: Backward-Looking Government NVL Entries

G1.3.1 Core Fields

Each federal department (CFO-Act-covered agency, plus any additional entities designated by statute) submits one or more quarterly Government NVL Entries with the following fields:

1. Total Assets Held (A_t)

Definition: aggregate fair value of assets under departmental control, as defined by current federal accounting standards.
Scope: includes financial assets, physical capital, and other resources recognized on the department's balance sheet.
Basis: same valuation basis and recognition rules as in departmental financial statements; the NVL does not redefine asset boundaries.

2. Total Liabilities Outstanding (L_t)

Definition: all obligations — legal and contingent — for which the department bears responsibility under current accounting standards, excluding the separately specified contingent obligations above the materiality threshold (field 5).
Scope: includes debt, payables, accrued obligations, and recognized provisions.

3. Total Appropriations Received (P_t)

Definition: congressionally authorized funding for the reporting period, on a budgetary basis consistent with current federal practice.
Scope: captures both new appropriations and any formal re-appropriations or rescissions, netted according to existing budget rules.

4. Total Expenditures Made (E_t)

Definition: actual outlays against appropriations for the reporting period, on an accrual basis consistent with federal accounting standards.
Scope: includes operating expenses, capital expenditures, and transfer payments at the department level.

5. Contingent Obligations Above Materiality Threshold (C_t)

Definition: the aggregated value of commitments, guarantees, and contingent liabilities whose notional exposure exceeds a materiality threshold specified by regulation.
Scope: presented as one or more summary lines per department (e.g., guarantees, loan programs, legal contingencies), with a standardized category code.

G1.3.2 NVL Schema

On the NVL, each Government NVL Entry is recorded as a structured record:

entity_id — department or agency identifier
period_start, period_end — reporting period
A_t, L_t, P_t, E_t, C_t — core numeric fields
currency, valuation_basis — metadata for units and valuation rules
audit_status — e.g., "unqualified," "qualified," "adverse," "in progress"
source_reference — pointer to the underlying departmental financial statement and audit report
classification_flag — indicates whether this record is fully public, includes consolidated classified components, or is itself a classified summary line
signature — cryptographic attestation by the department's CFO office and the independent auditor or Inspector General, as appropriate
version — allows amendments (e.g., restatements) to be tracked as new versions, never overwriting previous entries

The data model is deliberately minimal. The aim is not to expose every budget line, but to provide a summary mirror of CFO-level reporting that the NFB and NCOS governance layers can read directly.

G1.4 Process: From CFO Statements to NVL

G1.4.1 Reporting Cycle

Government NVL Reporting is aligned with existing federal fiscal cycles:

1. Departmental Close

Each department completes its quarterly close using current accounting systems and processes.
The close produces internal financial statements and is followed by audit or review procedures, as already required.

2. Summary Extraction

A standardized extraction process computes A_t, L_t, P_t, E_t, and C_t from the departmental statements.
This extraction can be implemented as a common software layer integrated with existing financial systems, or a centralized Treasury/OMB service that ingests departmental statements and produces NVL-ready summaries.

3. Attestation and Signing

The department CFO (or equivalent) and the relevant independent auditor/IG sign the summary digitally.
Audit status is recorded in the audit_status field.

4. NVL Publication

Signed summaries are written to the NVL's government partition in a batch at the close of each reporting period.
Once written, entries are immutable; any corrections are posted as new versions with explicit references.

5. Aggregation and NFB Integration

The NFB reads these entries as the expenditure-side inputs, integrating them with revenue-side data from private NVL entries.
S22 and other system-mechanics sigmoids consume these aggregates as part of their control logic.

G1.4.2 Classified Programs

Classified and sensitive programs are handled through structured aggregation:

Departments with classified components post a public departmental summary that includes a dedicated "classified programs" line inside P_t, E_t, and where applicable C_t.
The aggregate magnitude of the classified line is public. Its components are not.
A separately maintained classified partition — accessible only to cleared oversight personnel — holds the disaggregated classified entries.
Independent auditors with appropriate clearances attest to both the classified and public partitions, and the public audit opinion covers the department as a whole.

G1.5 The Completeness Extension: Ghost Appropriations

Section 5.8d establishes that under the Symmetry Protocol, an unregistered government appropriation is legally unauthorized for NVL-anchored operations.

This has two consequences:

1. Ghost Appropriations Are Structurally Prevented

Any spending that seeks to engage the NBUSA, benefit from NVL-based settlement, or appear in NCOS-governed fiscal reporting must trace to an NVL-registered appropriation.
Appropriations that are not recorded on the NVL cannot be processed through NBUSA channels and cannot be recognized in the NFB.

2. Public Debt Integrity

The NBUSA's capacitors and S22's debt governor operate on NVL-visible aggregates.
Ghost appropriations — spending outside the ledger — would otherwise introduce unmodeled claims on the national fiscal position; the Completeness Extension forecloses that failure mode.

In effect, the Symmetry Protocol symmetrizes the enforcement boundary:

For citizens: "unregistered wealth is inert."
For the state: "unregistered appropriations are fiscally invisible and operationally unsupported."

G1.6 Interaction with S22 (Debt Governor)

Section 5.8c notes that S22 currently operates on NVL-computed debt/GDP ratios updated on a quarterly cycle. Without Government NVL Reporting, S22's inputs are aggregated, lagged, and partially decoupled from actual spending trajectories.

Under the Symmetry Protocol:

S22 gains line-of-sight into departmental burn rates: how quickly each department is drawing down its appropriations over the quarter.
The Issuance Authority parameters (D_i) can be monitored against actual expenditure trajectories, rather than just ex post debt levels.

Importantly:

G1 does not change S22's parameters.
It improves the quality and timeliness of S22's sensor data.
The Fiscal Respirator function remains structurally intact; S22 simply receives finer-grained, ledger-native inputs.

This is consistent with NCOS's design philosophy: upgrade data quality before inventing new control laws.

G1.7 Forward-Looking Layer: Design and Governance

G1.7.1 Purpose and Separation

The forward-looking component consists of projections: next-year appropriations plans, multi-year obligation trajectories for major programs, and potential future commitments that, while not yet appropriated, are realistically contemplated within the planning horizon.

NCOS requires strict separation:

Backward-looking entries: audited, factual, binding as records; govern the calculation of the NFB, S22, and other sigmoids.
Forward-looking entries: labeled, non-binding projections; inform policy analysis, stress testing, and public understanding, but do not directly drive enforcement or canonical balances.

G1.7.2 NVL Representation

The forward-looking layer is implemented as a distinct NVL partition. Each projection record includes:

projection_id
entity_id (department or central authority)
horizon (e.g., FY+1, FY+2)
Projected P_(t+1), E_(t+1), and optional projected A_(t+1), L_(t+1) trajectories
projection_source — e.g., OMB, CBO-style office, or department
projection_status — "projected," "enacted," "replaced," etc.
binding_flag — always false for NCOS-level interpretations
assumption_set_id — pointer to the assumptions (growth, inflation, policy) used

These records are never co-mingled in the same table or namespace as audited historical entries. APIs and user interfaces must differentiate clearly between "record" and "plan".

G1.7.3 Role in NCOS Dynamics

NCOS v1.0 uses the forward-looking layer as:

An input to simulation and stress-testing, not to the canonical NFB.
A basis for early-warning indicators (e.g., if projected obligations imply a breach of S22 thresholds under plausible scenarios).
A tool for public scrutiny: citizens and analysts can compare projected appropriations and obligations to realized values, period by period.

The system must be designed so that if the forward-looking layer vanished tomorrow, NCOS would still be operationally complete. When present, the layer improves foresight without compromising the integrity of the record.

G1.8 Constitutional and Legal Reinforcement (C1)

Constitutional Note C1 frames the civic obligation as an excise on the privilege of accessing federal utility. The Symmetry Protocol strengthens this position in three ways.

G1.8.1 Reciprocity and Dole Nexus

When the NVL is a one-way registry, the state risks being seen as compelling detailed financial disclosure from citizens without any reciprocal obligation. Under the Symmetry Protocol:

The same ledger that records private wealth also records government stewardship.
The condition of participation is: "you may access this national financial infrastructure, but you join a ledger on which your obligations and the state's stewardship of those obligations are both visible."

This architecture buttresses the Dole-style nexus:

The condition (NVL registration) is tightly related to the benefit (access to a shared, symmetric fiscal infrastructure).
Citizens' obligations and the state's corresponding duties are co-located in a common data structure.

G1.8.2 Privacy and Proportionality

Symmetry strengthens NCOS's privacy posture:

The government does not ask for visibility it is unwilling to provide about itself at a comparable level of aggregation.
The system is less vulnerable to arguments that it is an overreaching surveillance infrastructure; instead, it is a mutual disclosure regime anchored in fiduciary norms.

G1.8.3 Government as Fiduciary, Made Structural

The Symmetry Protocol embeds the government's fiduciary duty into the same infrastructure:

The sovereign's fiscal position is a ledger-native object subject to the same cryptographic integrity and completeness rules as private positions.
This alignment supports due-process and fairness arguments: citizens are not subject to an asymmetrically opaque state.

G1.9 Failure Modes and Safeguards

G1.9.1 Gaming of Categories and Ghost Appropriations

Failure Mode: Departments reclassify items to avoid inclusion in the five fields, or execute spending against appropriations not recorded on the NVL.

Safeguards:

Tight coupling to existing accounting standards reduces interpretive slack.
Legal coupling: any appropriation or obligation engaging NVL/NBUSA infrastructure must be registered; unregistered spending cannot be processed through the federal fiscal backbone.
Auditors and oversight bodies can reconcile Government NVL Entries to departmental financial statements; discrepancies are themselves red flags.

G1.9.2 Classification Overreach

Failure Mode: The "classified" summary line becomes a dumping ground for politically inconvenient but non-security-related spending.

Safeguards:

Narrow statutory definition of what may be treated as classified in NVL reporting.
Soft caps on the total classified share of appropriations and expenditures.
Automatic review triggers if classified shares exceed defined thresholds, forcing IG and congressional oversight.
Cleared oversight bodies can inspect the fine-grained classified partition and verify that classification is properly used.

G1.9.3 Cybersecurity and Data Integrity

Failure Mode: Adversaries tamper with government NVL entries or disrupt public access.

Safeguards:

Separation of write-path (hardened, access-controlled) from read-path (separately cacheable and rate-limited).
Cryptographic integrity: entries are signed and hash-chained; any tampering is detectable.
Defense-in-depth consistent with federal cybersecurity standards; the NVL is treated as critical infrastructure.

G1.9.4 Political Resistance and Partial Adoption

Failure Mode: Agencies resist full implementation, resulting in incomplete reporting.

Safeguards:

Phased adoption: pilot with a small set of departments, then expand.
Public default expectation: absence of entries by non-reporting departments becomes visible and politically salient.
Statutory teeth: linking certain NBUSA and NVL-based benefits to compliance with Government NVL Reporting requirements.

G1.10 Minimum Research and Implementation Work for a Future Version

Five workstreams are required to move Government NVL Reporting from design to deployment:

a. CFO Act Field Mapping Produce a detailed mapping from standard departmental financial statements to A_t, L_t, P_t, E_t, and C_t, including edge cases (trust funds, cross-agency programs, multi-year appropriations). Validate across a representative sample of departments.

b. Comparative Survey of Open-Finance Governments Document how leading open-finance jurisdictions (Estonia, New Zealand, Nordic governments, OECD high-scorers) handle machine-readable government finance. Extract design lessons applicable to NVL implementation.

c. Prototype NVL Schema and Pilot Implementation Implement the Government NVL schema. Run a pilot with 2–3 departments, ingesting real historical data to test accuracy, timeliness, and integration with existing systems.

d. Failure Mode and Oversight Design Conduct a structured risk analysis on gaming, classification, and cyberattack scenarios. Formalize oversight mechanisms, triggers, and statutory language concepts.

e. Forward-Looking Layer Governance Proposal Define which bodies may publish projections to the NVL. Specify minimum standards for labeling, documentation of assumptions, and revision history. Recommend how these projections may and may not be used by NCOS governance.

G1.11 Conclusion: Symmetry as Architecture, Not Ornament

The Symmetry Protocol is not a transparency policy bolted onto an otherwise complete system. It is part of the architecture itself.

Without government NVL participation, the National Verified Ledger is a tax registry.
With it, the NVL becomes what NCOS requires it to be: a national financial ledger on which the obligations and stewardship of all participants — private and sovereign alike — are visible, verifiable, and permanent.

Technical Note G1 shows that implementing the Symmetry Protocol is feasible with the existing CFO Act infrastructure plus a bounded set of new technical and legal steps; strengthens NCOS's constitutional and privacy posture by making the state a co-tenant on the ledger it asks its citizens to inhabit; and closes the feedback loop that the NFB and S22 need to operate on honest, timely, ledger-native data.

For NCOS v1.0, the backward-looking core of Government NVL Reporting is mandatory and conceptually sufficient; the forward-looking layer is an architecturally supported enhancement, cleanly separated from the factual record. Together, they make Symmetry real — not decorative — and give the Republic a fiscal physics in which the same infrastructure that demands honesty from its citizens demands honesty from the state itself.

Technical Note G1 — NCOS Working Paper v1.0 companion document · ncos.world · November 2026 Companion documents: Working Paper v1.0 Section 5.8; Constitutional Note C1 (which cross-references G1 in its Dole analysis).