Review capabilities, approvals, grants and audit evidence from a console served by the host itself.
Experimental
Implemented foundations. Independent release work continues.
ConnectReviewDecideAudit
Illustrative mechanism. The diagram describes the product’s role, not a live execution.
HOW IT WORKS
A focused role. A clear boundary.
Review what this Mac exposes to agents, decide pending approvals and read the audit trail in a browser served by the host itself.
01
Connect
02
Review
03
Decide
04
Audit
⊙
The console displays and decides host-owned state; policy, execution and audit truth stay on this Mac. Experimental build; packaging and continuous verification are still in progress.
PRODUCT DEVELOPMENT
What’s here. What comes next.
BUILT SO FAR
The current foundation
Eighteen owner-facing views over the host console API: catalog, exposure, grant requests, pending approvals, grants, audit, evidence, tasks, sources, extensions, mesh, network and enterprise policy.
Same-origin console-key authentication over loopback; the key stays in the browser and is never logged or placed in a URL.
COMING NEXT
The next useful step
Bundle the console build into the packaged host so a clean install serves /console without a checkout.
Continuous CI verification and a recorded live-host smoke run before release.
Plans describe direction, not delivery dates. Verified support and release maturity vary by product.
PART OF POCKATE
Independent purpose. Shared foundations.
Pockate products are designed for independent adoption and composition. Companion connects these foundations to a local computer; authority stays with its enforcing host.