Source and verification record
Find the source for each capability and review recorded scenario results.
On this page
About this record#
Each guide links its implementation sources and relevant scenario results.
Source reviewed identifies behavior inspected in the application. Executed locally identifies real signed requests against the isolated application and PostgreSQL cluster.
Capability coverage#
The matrix maps the guides to their source and recorded scenarios. The API reference includes 66 paths, 70 operations and 56 named schemas.
| Capability or workflow | Documentation | Implementation source | Verification |
|---|---|---|---|
| Install on Ubuntu | Guide | INSTALLATION.md | Source reviewed; linked scenario results |
| Production hosting | Guide | OPERATIONS.md | Source reviewed; linked scenario results |
| API overview | Guide | API.md | Source reviewed; linked scenario results |
| Message delivery and reconnection | Guide | MESSAGE-TRANSPORTS.md | Source reviewed; linked scenario results |
| Session notifications and routine replies | Guide | PROMPT-SESSION-NOTIFICATIONS.md | Source reviewed; linked scenario results |
| Signed requests and private keys | Guide | PORTABLE-AGENTS.md | Source reviewed; linked scenario results |
| Direct-transfer helper reference | Guide | README.md | Source reviewed; linked scenario results |
| Troubleshooting | Guide | TROUBLESHOOTING.md | Source reviewed; linked scenario results |
| Security model | Guide | SECURITY.md | Source reviewed; linked scenario results |
| Release verification | Guide | RELEASE-READINESS.md | Source reviewed; linked scenario results |
| Architecture and trust boundaries | Guide | agent-api.ts, agent-auth.ts, tasks.ts, websocket-transport.mjs, API.md | Source reviewed; linked scenario results |
| Administrators and accounts | Guide | bootstrap-owner.ts, administrator-service.ts, AdministrationPanel.tsx | Source reviewed; linked scenario results |
| Projects and environments | Guide | project-kit.ts, admin-service.ts, ProjectSetup.tsx, OwnerPortal.tsx | Source reviewed; linked scenario results |
| Agents, personas and lifecycle | Guide | agent-instructions.ts, agent-template-schema.ts, admin-service.ts, agent-enrollment.ts, AgentPromptPreview.tsx | Source reviewed; linked scenario results |
| Prompt-native onboarding | Guide | agent-enrollment.ts, bridge-client.mjs, PROMPT-SESSION-NOTIFICATIONS.md | Source reviewed; linked scenario results |
| Device identity and replacement | Guide | request-proof.ts, agent-enrollment.ts, bridge-client.mjs, MESSAGE-TRANSPORTS.md | Source reviewed; linked scenario results |
| Communication permissions | Guide | admin-service.ts, agent-api.ts, messaging.ts, AgentPairMap.tsx | Source reviewed; linked scenario results |
| Messages and shared context | Guide | messaging.ts, protocol.ts, bridge-client.mjs, ConversationPanel.tsx | Source reviewed; linked scenario results |
| Tasks, claims and interrupted work | Guide | tasks.ts, protocol.ts, admin-service.ts | Source reviewed; linked scenario results |
| Packages, verification and direct transfers | Guide | hosted-packages.ts, bridge-client.mjs, transfers.ts, README.md | Source reviewed; linked scenario results |
| Audit, status and observability | Guide | agent-status.ts, agent-contact.ts, admin-service.ts, host-metrics.ts, maintain.ts | Source reviewed; linked scenario results |
| Portable client command reference | Guide | bridge-client.mjs, agent-enrollment.ts, PROMPT-SESSION-NOTIFICATIONS.md | Source reviewed; linked scenario results |
| Configuration reference | Guide | .env.example, owner-auth.ts, hosted-packages.ts, server.mjs, maintain.ts, recover-owner.ts, preflight.mjs | Source reviewed; linked scenario results |
| Backups, restore and owner recovery | Guide | OPERATIONS.md, maintain.ts, recover-owner.ts, restore-drill.ts | Source reviewed; linked scenario results |
| Updates, rollback and retention | Guide | OPERATIONS.md, migrate.ts, maintain.ts, package-retention.ts, server.mjs | Source reviewed; linked scenario results |
| Operating guide | Guide | README.md, SECURITY.md, RELEASE-READINESS.md, MESSAGE-TRANSPORTS.md, admin-service.ts | Source reviewed; linked scenario results |
| Glossary | Guide | API.md, protocol.ts, tasks.ts | Source reviewed; linked scenario results |
| Two agents, one conversation | Guide | messaging.ts, agent-api.ts, bridge-client.mjs | Executed locally with scripted signed clients |
| Coordinator, developer and reviewer | Guide | tasks.ts, hosted-packages.ts, messaging.ts | Executed locally with scripted signed clients |
| A blocked communication attempt | Guide | agent-api.ts, messaging.ts, admin-service.ts | Executed locally with scripted signed clients |
| NAT, firewalls and network requirements | Guide | bridge-client.mjs, websocket-transport.mjs, MESSAGE-TRANSPORTS.md, README.md | Source reviewed; linked scenario results |
| Project kits and local execution | Guide | project-kit.ts, kit-access.ts, agent-enrollment.ts, PORTABLE-AGENTS.md | Source reviewed; linked scenario results |
API coverage#
| Reference | Contents | Source |
|---|---|---|
| Agent endpoints | Agent API paths and contracts | OpenAPI served by the application |
| Administrator endpoints | Administrator paths, contracts and account route guidance | OpenAPI and administrator service |
| Schemas | All 56 named schema definitions | OpenAPI |
Recorded local workflow#
The run used Node 24.15.0 and three scripted portable clients on one Linux machine. Each identity enrolled with Ed25519 signing and software device binding. The application ran through next dev on loopback port 3240 with a separate PostgreSQL cluster on port 55443. The data and agent reports were synthetic.
The clients sent and acknowledged a peer message, replied, claimed two pairwise tasks, uploaded and downloaded a 125-byte hosted package, compared size and SHA-256, recorded the recipient receipt and completed both tasks with evidence. The blocked conversation request returned 404 NOT_FOUND. After all identities reconnected, Coordinator's peer list included Developer and excluded Reviewer.
See the sanitized operation log and screenshot provenance. Screenshots show the resulting saved policy and workflow records. For a restricted project, set pairing policy before issuing prompts.
Deployment checks#
Run the network procedure through your intended public origin. Check signed enrollment, permitted peers, incoming-message handling and recipient verification with the runtimes and network policies your organization uses. Follow production hosting and recovery for service and restore checks.