Daedro / Handbook
Chapters
HandbookChapterRead Markdown ↗

Test readiness and consulting handoff

Updated November 4, 2026. Engineering owns Daedro; the consulting workspace owns sales and its order registry. Flowdesk at https://flowdesk.rokenshi.com/case is a separate Worker/D1 demonstration and is not evidence of Daedro cloud readiness.

Available now

Local marketplace: http://127.0.0.1:8791/ . Handbook: http://127.0.0.1:8791/docs . Both returned HTTP 200 after restarting the local server. Reproduce with make build followed by ./bin/daedro-mcp-hub serve --port 8791 from the repository root. This command starts the catalogue/documentation, not a configured secret broker.

Local OpenBao integration evidence: commit 8b536da; real OpenBao 2.7.0 synthetic checks passed for TLS, single-use SecretID, a 300-second token, cross-workspace refusal and revocation. make test build passed, including Go race tests and vet. The synthetic OpenBao store was left sealed. No real API credential was migrated.

Cloud deployment record: commit 3906eab and deploy/gcp/README.md. One secrets VM exists with a 24-hour STOP policy; cloud OpenBao readiness has not been confirmed. There is no public hub deployment or public acceptance URL yet.

The private secrets command now connects OpenBao TOTP authentication, entity-to- workspace authorization, single-use AppRole issuance, pinned secret reads, pre-execution revocation and a hash-pinned stdio MCP process. The server-rendered UI provides login, verification, run status and logout. See configuration and limits. Automated fixtures are synthetic; this does not establish live cloud or real-provider acceptance.

Agreed first scenario

Coordination contract: CONSALTING/handoffs/daedro-mcp-demo-contract-2026-11-04.md. Prefer an already-supported source-retrieval MCP on public fixtures; the supported S3 read-only integration is the fallback. Implement one scenario only. No Gmail, customer data, arbitrary uploads, external writes or new AI generation is needed. The result must include a source/object reference, run ID, timestamp, duration and explicit status. Flowdesk does not need to become an MCP client.

First release acceptance — not yet passed

  1. A user signs in with enforced MFA and creates a private workspace.
  2. The user stores a restricted real API key; neither the list nor logs reveal it.
  3. The user grants one approved read-only MCP access and runs a bounded API call.
  4. Another workspace cannot read the secret or invoke the private deployment.
  5. Revoke the grant and stop the MCP: new executions fail with a useful redacted error. Revoke the external provider key separately if invalidating previously copied plaintext is required. Export a redacted audit trail.

Required before calling this ready: verified cloud OpenBao and recovery custody, workload role provisioning, restricted network egress, live MFA enrollment and configuration of the implemented private UI/runtime, then a real-provider end-to-end test of the steps above. A five-minute OpenBao token does not make the external API key expire after five minutes.

What may be shown to prospects

The local catalogue and tested backend building blocks may be presented as work in progress. Do not claim a ready multi-tenant hosted secret manager, production security certification, customer outcomes, or a finished public hub. No customer outreach or modification to Flowdesk is authorized by this handoff.

Current execution constraint

Cloud Shell was successfully started and authorized by this chat. Browser-control tooling subsequently became unavailable; local gcloud is not installed or signed in. Do not claim that this was an incomplete user setup. Verify the existing VM before issuing any further cloud create operation; do not duplicate it.