Docs

Publicus trust docs

Human-readable operating record for the open trust substrate: how evidence is read, how the source contract works, what changed, and where the 2026 program is going.

Start by job

Publicus should be readable before someone understands the whole trust substrate.

Scan a package or stackCheck one AI-suggested dependency or upload manifests, lockfiles, requirements files, TOML, or SBOMs. Check one packageInspect curated status, advisories, project health, and provenance expectations. See exploited risksReview Publicus-tracked AI components with public exploitation pressure. Understand Canada review readinessMap evidence to procurement, cyber, AI/ML supply-chain, and responsible-use questions.

How to read the system

Why Publicus is differentHow Publicus stays valuable when advanced cyber models and open model tooling become broadly available.
How to read PublicusStatus semantics, curated truth versus live enrichment, and the role of bounded synthesis.
Canada release readinessHow scan evidence maps to Canadian review context without claiming certification.
Evidence pack formatJSON and Markdown export shape for package scans, review proposals, and readiness evidence.
Project evolutionSanitized history from signed YAML registry to scan-first public trust substrate, including what must not regress.
Product redesign prototypeAI-native UX, wireframes, interaction design, event taxonomy, performance budgets, and implementation gates.
Reference plan snapshotA historical repo-only thesis and interface reference. Current work is outcome-gated through the docs router, decision log, and lineage index.
Governance modelHow contributions, review, and public promotion work today and where reviewer-council governance is heading.

Evidence and movement

Security source coverageEvery tracked security portal, primary URL, coverage state, blocker, and whether it is globally monitored or scan/lookup-only.
Weekly briefCurrent movement, source coverage, and standards progress in one readable page.
Recent changesRecorded movement from advisory drift and source/context observations.
NIST AI RMF crosswalkMachine-readable mapping from registry status to a standards artifact.

Canada and stewardship

Canada mappingHow registry status language translates into Canadian procurement, policy, and deployment-review context.
Open trust doctrineThe public doctrine behind signed evidence and inspectable trust decisions.
Trusted actor programThe sequencing model for broader open-source contribution without unreviewed trust-graph mutation.
Stewarded OSS safeguardsHow the project handles open contribution without weakening the trust graph.
Reviewer councilThe intended public review model for broader institutional legitimacy.
TransparencyWhat is published, what is measured, and what remains intentionally out of scope.

Reference

Registry browserEvidence-first component review.
Dependency scanCheck a single package or upload package manifests, lockfiles, and supported SBOMs to get a fix-first release audit.
Exploited risksPublicus AI-stack intersections with CISA Known Exploited Vulnerabilities.
Ask PublicusSecondary scoped synthesis over Publicus evidence after scan or inspection.
API referenceSwagger UI for the read-only trust API.
Operating recordCanonical project state is summarized through curated public docs, not generated archive pages.