The User Guide is the day-to-day operating manual for everyone who works in the platform. The same pages are bundled into the portal’s in-app help at runtime, so what you see here matches what you see when you press the help button inside the product.
If you’re brand new, start with Market Archetypes And Coworkers, then Getting Started. The other sections are organized by the work you do, not by the screens you click.
Start here
- Market Archetypes And Coworkers — how the selected business type shapes the portal, workspace, vocabulary, coworkers, voice, and marketing posture.
- Getting Started — what the platform does, how navigation works, and where your AI coworker lives.
- Roles & Access — the platform roles and what each one can do.
- AI Coworker — working with the context-aware assistant on every screen.
- Development Workspace — how Build Studio, VS Code, policy states, and validation environments fit together.
Domain guides
Each of these is the operating manual for one part of the platform. The pages are written for the people doing the work — admins for admin-only screens, finance leads for finance, and so on.
| Section | What it covers |
|---|---|
| AI Workforce | Provider configuration, model routing lifecycle, decision perspective, cost governance, and per-provider notes (Anthropic, Codex/OpenAI, xAI/Grok, local models). |
| Build Studio | The guided five-phase pipeline (intake, design, build, review, ship), Build runtime, documentation impact, and deployment. |
| Compliance | Regulations, controls, evidence, audits, incidents, regulatory submissions. |
| Customers | Customer accounts, sales pipeline, marketing. |
| Finance | Invoicing, AP/AR, banking and reconciliation, AI spend, controls and automation, reporting. |
| HR | Employees, roles, lifecycle scaffolding. |
| Operations | Delivery backlog, infrastructure discovery, value-stream operations. |
| Platform | AI operations, Edge Nodes, identity & access, authority & audit, tools & integrations. |
| Portfolios | Portfolio management, health metrics, investment tracking. |
| Products | Product inventory, lifecycle stages, business-model roles. |
| Security Operations | The built-in AI SOC — sources, detections, cases, governed response, compliance, and MSP federation. |
| Storefront | Public-facing storefront — setup, catalog, inbox, fulfilment, business and operations settings. |
| Wiki | Governed platform knowledge, founder-kernel pages, principles, and citations. |
| Workspace | The personal workspace, managed documents, and cross-domain activity. |
| Admin | Admin-only configuration screens. |
Architecture and standards
The runtime architecture, the Trusted AI Kernel (TAK), the Global AI Agent Identification & Governance (GAID) standard, and the platform’s conformance assessment live under the Architecture section.
Specifications and plans
Long-form design specs, audits, and implementation plans are kept in the source repository under docs/superpowers/. They are historical records of how each capability was built, not onboarding material - useful if you want to understand a design decision but not necessary to use the platform.
Documentation freshness
Documentation is part of DPF’s delivery definition of done. Build Studio and external Claude, Codex, and Grok implementation threads update the user guide, public site, architecture docs, AGENTS.md, or implementation history when a change affects those audiences. If a change does not need docs, the build or PR records a concrete no-docs-needed reason.