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 review-kit
PYTHONPATH=src python3 -m info_tech_canon alignment-template
PYTHONPATH=src python3 -m info_tech_canon validate
PYTHONPATH=src python3 -m info_tech_canon capability-review /path/to/record.json
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 /review-kit
• GET /alignment-template
• GET /validate
• GET /capability-review?path=
• 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/
• consumer alignment review kit in agent/review-kit/
• consumer alignment workplan template in agent/templates/

Alignment Reviews

The consumer alignment review kit lives under infospace/agent/review-kit/. It provides a repeatable workflow, model and standard selection guide, scorecard, structured review schema, and repo-local workplan template so agents can review consumer repositories against the canon without mixing consumer work into this repo.

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.

Consumer-filed reports on whether existing canon concepts provided utility live under feedback/. That directory is PurposeFit evidence, not a change request and not a canon artifact. A need still belongs in demand/; a body of knowledge still belongs in incoming/.

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.

repo-scoping adds a canon comparison and extension pack for repository intent, current scope, future scope, consumer purposes, review decisions, evidence, source observations, utility relationships, scope freshness, and SCOPE.md as an interface profile. The pack is intended to seed the consumer-side repo-scoping workplan while keeping proposed canon extensions reviewable.

Benchmarks

CARING benchmark assets live under infospace/standards/caring/benchmarks/. The first benchmark is kubernetes-rbac, which maps Kubernetes RBAC native constructs into CARING descriptors and records canon pressure around native roles, effective access, derived workload capabilities, induced secret exposure, and the rule that a Namespace is not automatically a tenant boundary.