Building interoperable, adaptable, and extensible information-processing systems.

Current Service

This repository now implements one concrete infospace under infospace/. The repository root remains the service, governance, and workplan shell.

The first service surface is intentionally small:

• JSON-first CLI commands
• importable Python service functions
• read-only local HTTP API
• artifact loading, checks, and graph summaries backed by infospace-bench

Source-Tree Usage

PYTHONPATH=src python3 -m info_tech_canon inspect
PYTHONPATH=src python3 -m info_tech_canon artifacts
PYTHONPATH=src python3 -m info_tech_canon models
PYTHONPATH=src python3 -m info_tech_canon standards
PYTHONPATH=src python3 -m info_tech_canon validate
PYTHONPATH=src python3 -m info_tech_canon graph
PYTHONPATH=src python3 -m info_tech_canon index
PYTHONPATH=src python3 -m info_tech_canon views
PYTHONPATH=src python3 -m info_tech_canon profile inspect small-saas
PYTHONPATH=src python3 -m info_tech_canon profile validate small-saas
PYTHONPATH=src python3 -m info_tech_canon profile graph small-saas
PYTHONPATH=src python3 -m info_tech_canon api --host 127.0.0.1 --port 8765

After package installation, the same commands are available through the info-tech-canon console script.

API Endpoints

• GET /health
• GET /inspect
• GET /artifacts
• GET /artifacts?kind=model
• GET /models
• GET /standards
• GET /validate
• GET /graph
• GET /graph?format=mermaid
• GET /views
• GET /views/{name}
• GET /profiles/{profile}/inspect
• GET /profiles/{profile}/validate
• GET /profiles/{profile}/graph

Maintenance

make validate
make index
make tree
make agent-briefs

First Profile Proof

The first executable profile proof is small-saas. It lives under infospace/profiles/small-saas/ and includes connected example artifacts for a tenant-aware SaaS service: service, system, tenants, user, team, dataset, deployment, task, policy, control, evidence, and incident.

Agent Retrieval

Agent-facing retrieval assets live under infospace/agent/:

• global-agent-brief.md
• retrieval-index.md, retrieval-index.yaml, and retrieval-index.json
• per-artifact briefs in agent/briefs/
• consumer brief templates in agent/consumer-briefs/
• Canon Interface Card template in agent/templates/

Purpose And Demand

The PURPOSES candidate model is registered as a governance extension at infospace/models/governance/InfoTechCanonPurposeDemandExtension.md. It defines consumer purposes, demand signals, purpose fit, scope pressure, and evolution requests so consumer demand can inform repo governance without silently changing producer scope.

Evaluations

Canon-side evaluation packs live under infospace/evaluations/. The first pack is user-engine, which prepares pre-integration assessment of a user-management capability against Organization, Access Control, Governance, Data, Security, Task, PURPOSES, CARING, and the small-saas profile.

railiance-fabric adds conformance support for graph-oriented entity and edge capture, including mapping expectations and visualization examples that separate canonical relationships from display-only graph edges.