Transparency
What Publicus shows today
The trust surface is useful now, but still early. This page is explicit about what is live, what remains thin, and what still needs to deepen before launch-grade institutional claims.
Already public
- Registry entries, advisories, exploited-risk intersections, and public movement feed.
- Human docs and API docs as distinct surfaces.
- Source-contract metadata for vulnerability, package, provenance, project-health, Canada-context, and standards evidence families.
- First machine-readable NIST AI RMF crosswalk artifact.
Still shallow
- Several source families are object-specific lookups rather than global feeds.
- Project-health and provenance layers are visible but need broader component coverage.
- The weekly "what changed" discipline still needs to become routine and automatically generated.
- Governance is public, but reviewer-council operations are not yet fully institutionalized.
How to verify
Start with the public source contract, recent-changes feed, and plan of work. Those pages show what Publicus claims, what is sourced, and what still needs to mature.
Inspect the source contract · Review recent changes · Read the plan of work