What an authorization really is — shown, not just told

Package journey — illustrative sequence

How the package comes together

Press play, or drag the month line. Two illustrative paths run against the same calendar — a typical 18-month effort and a 9-month accelerator. Watch what enters the package at each stage, and where the model stops so a human can decide.

The point of comparison: at month 18 on the calendar, the typical path is just reaching its authorization decision — the accelerator path reached its decision at month 9 and has nine months of continuous monitoring behind it.

Both timelines are planning illustrations. Actual duration depends on scope, evidence quality, assessment findings, remediation, and authorizing-official decisions; an accelerator does not guarantee authorization. Continuous monitoring begins after authorization and continues thereafter. Phase boundaries shown are illustrative placements, not published durations.

The guided path reads the sixteen package documents two at a time. It is an orientation through the governed catalog, not an automated authorization workflow.

Executable governed model

Ask the model what it knows

These are the questions everyone actually asks. Click one and watch the model answer honestly — with its real state, its real refusal codes, and the exact human act that would change the answer. The refusals are the demonstration.

Reference inputs

3 mapped — 19 withheld

CORE admission

0 admitted — 9 refused

EXTENDED admission

0 admitted — 14 refused

Open gaps

25 every one enumerated in the record

Active refusals

25 every one enumerated in the record

Authority created

No the model cannot create it

Fail-closed result: most source claims have no explicit Reference-registry mapping, so dependent CORE and Extended claims remain blocked. Public silence is not converted into a negative conclusion.

One governed source

Who gets to say what

Every fact on this page resolves through one ordered sequence, and each layer has a job it cannot exceed. A lower layer cannot silently override a higher-authority rule, and projections remain outputs — never independent authorities.

1. 1Core masterThe non-negotiable rules of the framework itself.
2. 2Validated extended profilesReusable implementation patterns — candidates, never assumptions.
3. 3Validated instance factsWhat this particular system actually chose and configured.
4. 4Recorded human judgmentA person's decision, on the record. The resolver may carry it — it can never write it.
5. 5Resolved authorization modelEverything above, joined into one consistent picture.
6. 6Document projections — outputs onlyThe papers the picture can print. Paper carries authority; it never creates it.

One control, end to end

One rule, followed home

Take one familiar rule — accounts must be managed, NIST AC-2 — and follow it through every layer. Watch what each layer is allowed to contribute, and where the trail stops at a person.

1. AUTHORITATIVE SOURCE

   The rule exists

   NIST publishes the requirement; the framework gives it a seat in the model.

   NIST-AC-2 is the external requirement identifier. The federal RMF-style CORE concept remains CTRL-005.

2. EXTENDED REUSABLE PROFILE

   A way to meet it is on offer

   A reusable identity pattern — RBAC, MFA, privileged access management — waits as a candidate, nothing more.

   AZGOV-FRH.IDENTITY.ENTRA-RBAC-MFA-PIM — the bounded pattern was admitted only after applicability validation.

3. GULF FICTIONAL IMPLEMENTATION

   The fictional system picks it

   The specimen selects the pattern and points at a synthetic piece of evidence.

   INST-IDENTITY-001 selects the pattern and EVID-FIX-IDENTITY-001 supplies a synthetic evidence pointer.

4. HUMAN JUDGMENT

   A person says it applies

   Someone — fictional here, real in practice — records the applicability call. The machine only remembers it.

   JUDG-APPL-IDENTITY-001 records APPLICABLE_TO_FICTIONAL_EXERCISE. The resolver did not create that judgment.

5. CLOUD WAYPOINT INTERPRETATION

   Resolved — and no further

   The model can now carry the approved applicability. Tested and accepted remain open, because no one has tested or accepted anything.

   RES-IDENTITY-001 carries the approved fictional applicability. Assessed and accepted remain not established.

Change a fictional assumption

Pull one thread

Assumption: the fictional identity selection or its synthetic evidence changes. One small change — and the honest cost is visible: 65 dependency paths re-checked, 6 people who must look again, 15 documents stale until they do. Invalidate the resolved value and re-run applicability and human-review gates before regenerating affected projections. Nothing regenerates itself past a human gate.

Build a package from the model

Sixteen documents, one honest shelf

The package is sixteen documents, GULF-00 through GULF-15. In this empty specimen, one previews and fifteen refuse to render — correctly — because rendering them would require evidence or judgment the specimen doesn't hold. Every projection, previewed or refused, carries the required fictional marking in full, exactly as it appears in the banner at the top of this page.

OSCAL

A format that travels — and knows its place

The envelope is proven to travel: a schema-valid, lossless OSCAL 1.2.3 test envelope is verified for transport only; semantic package compatibility is not established. What it may never do is impersonate an authorization — package export remains refused, because no format converts assembly into authority. The FedRAMP OSCAL 1.2.2 reference is a vendored control-catalog version, not a package consumer contract.

Transport compatibility

VERIFIED

Package export

REFUSED

Creates authorization facts

NO

Sources

What the model believes — and why so little

The model currently believes exactly three public documents — each mapped, dated, and bounded. Nineteen more claims exist, and every one stays withheld until it earns a registry mapping. Freshness is recalculated by that registry as of 2026-08-30T23:59:59Z; embedded GULF freshness is never trusted. Belief is expensive here, on purpose.

Words on this page

The vocabulary, in plain terms