For CitizensFor LegislatorsLibraryContact
For implementers

Build systems whose capability stays inside necessity and authority

For state CIOs, architects, procurement officers and vendors: the standard, patterns, contract requirements and tests that turn the model acts into systems.

The governing relationship

A system is usually judged by function, cost, security, usability and legal compliance. Fiduciary Commons adds a prior question: what standing power to know will this system give government, and is that power both legitimate and necessary?

STIC ≤ NSIC ≤ SLIA

TermPlain meaning
Standing Technical Informational Capability (STIC)What the deployed system can routinely do under ordinary permissions, including administrators, vendors and AI agents.
Necessary Standing Informational Capability (NSIC)What the legitimate function actually needs to be able to do routinely.
Standing Legitimate Informational Authority (SLIA)What government may legitimately do. Legal authority sets this outer ceiling; it does not instruct government to build everything that fits beneath it.

The Authority-Capability Correspondence Principle tests deployed capability against necessity-bounded authority. Where a less informationally powerful architecture can perform the legitimate function, that is the architecture to build.

Materials

Design patterns

No phone-home, authorized answer, query-without-collection, holder-controlled credentials and renewed authority.

Conformance test suite

Tests CF-01 through CF-79, assessed against actual capability and evidence rather than policy assertions.

Five-stage progression from delegated public authority through Fiduciary Commons, Ordered Informational Authority and the Authority-Capability Correspondence Principle to FCGIAS
Figure 1. From delegated authority to FCGIAS, Version 2.2.