APCP began as a publishing router: take an artifact, verify it, approve it, and prepare it for the destinations where it belongs. That still matters. Substack, Medium, LinkedIn, X, Facebook, YouTube, GitHub, Cloudflare Pages, and owned sites all have different formats, rules, and handoff requirements.
But government directories, bill research, source maps, and claim graphs are not publication problems first. They are source problems. Their first question is not "where should this go?" It is "what do we know, where did it come from, when was it checked, and what depends on it?"
The Split
APCP is the Publication Control Plane. It governs outward motion: approval, destination mapping, announcements, promotional packages, and assisted distribution.
The Sources Control Plane governs the layer before publication: official URLs, citations, claim status, freshness, conflicting sources, source snapshots, verification notes, and downstream usage. A source package should be reusable by Article Studio, Civic Studio, Newsletter Studio, or any future publication surface.
Why It Matters
If a bill changes status, a mayor leaves office, a department head changes, or a salary table is updated, the publishing system should not have to rediscover the world. The source package should know what changed and which publication drafts relied on the old fact.
That is the architectural boundary:
- Sources Control Plane: source truth, claims, citations, freshness, verification.
- APCP: approved language, destination formats, announcements, publication records.
The First Bridge
The first live bridge is in Bill & Law Studio. It creates a source-reviewed bill/law package and previews the Article Studio draft that could be generated from it. The draft is not the source record. It is a downstream publication candidate.
That distinction is small, but it changes the product. The sources can improve over time. The publication can be reissued, updated, or withdrawn. The system remembers why.