Operational architecture
Find the next governance decision, the module that supports it, and the artifact the accountable team should retain. Status labels distinguish working product surfaces from reusable foundations and unresolved research.
P0-P3 delivery ledger
Each phase is assessed laterally across platform behavior, interface exposure, user workflow, and remaining risk. Labels describe the delivered capability, not certification or regulatory completeness.
Deterministic validation, allowlisted build, release manifest, and deployable dist.
Shared assets use one release identifier; no new operating workflow.
Broken files, fragments, metadata, and mixed asset versions block release.
External services and hosting headers remain outside GitHub Pages control.
Versioned Case File and Evidence Bundle with local import, merge, handoff, and export.
Onboarding, Assessment Path, and PALO-AM expose case and evidence controls.
A case can move from orientation to assessment, simulation, and board review.
Browser storage is not encrypted collaboration or an assurance repository.
Structured starter libraries, worked cases, templates, contracts, and connector patterns.
Artifacts are public and linked, but no live connector or library-management UI is claimed.
Teams can begin from consistent records instead of inventing formats independently.
Thresholds and examples require local calibration and accountable source review.
Public topology plus navigation entities and relations in the primary Explorer.
Intent filters, status ledger, graph mode, inspector properties, and table fallback.
Visitors can start from a decision or artifact instead of guessing a page name.
The map improves discovery; it does not automate governance judgment or prove completeness.
Accessible equivalent
This complete text view follows the same filters as the topology and remains usable without interpreting spatial relationships.
| Intent | Stakeholder | Phase | Destination | Artifact | State |
|---|---|---|---|---|---|
| Define the use case | Accountable owner | Frame | AI Model Canvas | Use-case brief | Implemented |
| Find a practical route | Any stakeholder | Frame | Stakeholder Onboarding | Local route record | Implemented |
| Locate source guidance | Assurance and board | Frame | Documentation Hub | Source context | Implemented |
| Establish a risk route | Risk and legal | Classify | Risk Tiering | Risk report | Implemented |
| Evaluate rights impacts | Risk and legal | Assess | FRIA Assessment | FRIA record | Implemented |
| Bound delegated action | Product and engineering | Assess | PALO-AM | Agentic evidence plan | Implemented |
| Select owned controls | Product and engineering | Control | Control Library | Control plan | Foundation |
| Govern AI-assisted delivery | Product and engineering | Control | Vibe Coding | Delivery controls | Implemented |
| Define indicators | Assurance and board | Measure | KPI/KRI Generator | Indicator register | Implemented |
| Assemble the record | Assurance and board | Prove | Assessment Path | Evidence Bundle | Implemented |
| Receive monitoring signals | Risk and legal | Measure | PolicyWatcherContract: local signal schema Boundary: non-authoritative; pending human review | Monitoring signal | Foundation |
| Run accountable review | Accountable owner | Prove | Decision Gates | Gate decision | Foundation |
Public implementation record
Separate civic-tech portal and external monitoring companion. Signals remain non-authoritative until the primary policy and relevance are reviewed.
Research boundary
PALO provides educational governance support and portable evidence structures. These areas remain open programs, not completed product claims.
PALO FRAMEWORK