facetted-interfaces/history/FIAM_v0.2_Draft6

FIAM v0.2-draft.6 — Catalog Operations & Policy

Implementation draft of the Faceted Interface Architecture Model focused on safe continuous catalog operation and architecture-control queries.

fiam_version remains 0.2. The Core is frozen and byte-identical to the v0.2 draft baseline. Draft.6 changes profiles, policies, index semantics, adapters, and lenses—not Core entities.

What draft.6 adds

• scoped Snapshot Authority Policy: source + observation scope + population + domain;
• repeated-absence + grace closure, with last_seen distinct from closed_at;
• multi-scope observation union into one logical architectural edge;
• versioned Catalog Exchange Profile for YAML/JSON/NDJSON operational interchange;
• direct index-native Catalog Exchange ingest/export; whole-model YAML is no longer the operational write-ahead log;
• raw-evidence persistence with query-time scoring policy id/hash;
• generic declaration matching across Channel mediation, gateways, and working-set identities;
• automatic deployment environment/cluster/namespace Zone derivation from runtime identity tuples;
• Architecture Policy Lens for materiality and boundary-governance rules;
• Operation Coverage Lens for observed/dormant/never-observed declarations;
• Evidence Health Lens for conflict, challenge, staleness, and weak evidence;
• Security Evidence Coverage Lens that preserves runtime authentication unknown;
• explicit derived-index retention/purge contract.

Main documents

• FIAM-v0.2-Draft6.md — design/status memo and operational decisions.
• SNAPSHOT-AUTHORITY-v0.2.md — completeness authority, overlap, clocks, and grace.
• CATALOG-EXCHANGE-PROFILE-v0.2.md — versioned operational exchange contract.
• ARCHITECTURE-INTELLIGENCE-INDEX-v0.2.md — derived persistent query plane.
• DECLARATION-MATCHING-v0.2.md — historical declaration matching semantics.
• POLICY-INTELLIGENCE-LENSES-v0.2.md — materiality, compliance, coverage, evidence health.
• EVIDENCE-SCORING-v0.2.md — query-time evidence-strength policy.
• TEMPORAL-QUERY-LENSES-v0.2.md — architecture change and boundary drift.
• RUNTIME-CATALOG-v0.2.md — aggregate/runtime catalog write path.
• WORKING-SET-v0.2.md — non-destructive preferred-id projection.
• SEMANTIC-REGRESSION.md — executable guarantees.

Repository structure

canon/          controlled vocabulary + semantic policies
schemas/        frozen Core plus profile/policy/result schemas
lenses/         executable Lens definitions
policies/       authority, evidence, governance, Core freeze, shape identity
specimens/      semantic regression corpus
real-world/     ingest, authority, declaration, catalog, and query fixtures
tools/          adapters, exchange/index tools, validators, lenses, harness
history/        previous draft memos

Run conformance

make check

The checked result is CONFORMANCE.txt. The current reference run completes in roughly tens of seconds; the set-oriented fixture is a correctness smoke test, not a performance benchmark.

Operational Catalog Exchange example

python tools/catalog_index.py ingest-exchange estate.sqlite \
  real-world/catalog-exchange/runtime-2026-09-01.yaml \
  --authority-policy policies/SNAPSHOT-AUTHORITY-v0.2.yaml

python tools/catalog_index.py ingest-exchange estate.sqlite \
  real-world/catalog-exchange/runtime-2026-09-08.yaml \
  --authority-policy policies/SNAPSHOT-AUTHORITY-v0.2.yaml

python tools/architecture_changes_lens.py estate.sqlite \
  --population prod-cluster-a \
  --since 2026-09-07T00:00:00Z --until 2026-09-09T23:59:59Z \
  -o changes.yaml

Incremental feeds do not need completeness authority. A complete-snapshot is accepted only when its source/scope/population/domains are granted by the authority policy.

Direct NDJSON path

python tools/catalog_exchange.py convert input.yaml -o stream.ndjson \
  --input-format yaml --format ndjson

python tools/catalog_index.py ingest-exchange estate.sqlite stream.ndjson \
  --format ndjson --authority-policy policies/SNAPSHOT-AUTHORITY-v0.2.yaml

Reference architecture-control outputs

real-world/catalog-operations/ contains reproducible outputs for:

• appeared/disappeared/newly-undeclared dependencies;
• trust/organization boundary drift;
• policy materiality and violation;
• 90-day operation dormancy/never-observed coverage;
• security runtime-evidence unknown;
• evidence conflict/challenge/staleness;
• Catalog Exchange export.

Design posture

FIAM Core facts, Catalog Exchange records, index projections, and policy findings are deliberately separate. Do not add Core entities because an operational query is difficult. First ask whether the missing capability belongs to authority, exchange, indexing, reconciliation, evidence policy, Zone derivation, or a Lens.