Appearance
Built and planned
This page is the status reference for every other page in these docs. When another page and this page disagree, this page wins.
Last checked: October 15, 2026, against the development branch at commit 699f5236.
DutyGraph labels every capability in these docs.
- Built: in the code, with tests.
- Partial: some of it is Built and the rest is Planned. The row says which part.
- Simulated: the screen works, but no real outside system is connected.
- Planned: written down, not built.
WARNING
"Built" means the code exists and its tests pass. It does not mean a customer runs it in production. These docs make no claim about customers, results or certifications.
Map the company
| Capability | Status | Page |
|---|---|---|
| Add a company by its website; research with sources; Company Snapshot | Built | Company research |
| Research refresh plans, Refresh now, Keep research current | Built | Company research |
| Live news and competitor feeds | Planned | Company research |
| Sponsor packet: private link, voice with captions, team CSV, Here's what we heard | Built | Sponsor packet |
| Send me a test before the real send | Planned | Sponsor packet |
| Kickoff agenda, invitations, calendar file, pre-read page | Built | Executive kickoff |
| Kickoff transcript | Partial: paste only; file upload, audio and recorder import are Planned | Executive kickoff |
| Team asks on a phone, hours as tap ranges, answers stored "as understood" | Built | Team asks |
| Company Repo with eight file states, To review, Download your company | Built | Company Repo |
| Rule packs and an import receipt compiled into the Repo | Planned | Company Repo |
Task Cards with [H], [A] and [S] steps and AI modes | Built | Task Cards |
| Work Map: value chain, work flows, Task Cards, people, RACI | Built | Work Map |
| Top-down discovery designed around a functional organization | Built | Three ways in, one model |
| Pod-down discovery: one department sponsors a bounded unit | Planned | Three ways in, one model |
| Bottom-up task capture when an agent request has no adequate Task Card | Planned. The request tools are Built; capture, manager confirmation and application-owner validation are not | Just-in-time task capture |
| Matrix organization shapes; fully AI-run capture sessions | Planned | Map the company |
| Mission lineage: each task linked to why it exists | Planned | Task Cards |
Find opportunities
| Capability | Status | Page |
|---|---|---|
| Reported hours, the code-only AI-fit pass, proposed agents | Built | Opportunities |
| Hours with an agent | Simulated: authored values in the sample companies only | Opportunities |
| Possible constraints, Strategy exhibits (RACI, Theory of Constraints, SWOT / TOWS), DutyGraph Agent | Built | Outcomes and Strategy |
| Other framework exhibits; scheduled weekly invitations | Planned | Outcomes and Strategy |
| Route: the cheapest change that can work, by code | Built | Route |
| Reports: Prepare, Saved, Deliver, first view, Print / Save as PDF | Built | Reports |
Build agents
| Capability | Status | Page |
|---|---|---|
| Proposed agents, builder, versioned and hashed manifests, freshness | Built | Agent builder and manifests |
| Private 30-day agent plan link for the person | Built | Share the agent plan |
| Five export formats with README and GAPS files | Built | Exports and runtimes |
| Copilot declarative agent package; hosted agents on the company's vendor account | Planned | Exports and runtimes |
Govern agents
The aim is that every permission an agent holds is necessary for confirmed work, justified, approved and controlled. Today DutyGraph keeps an agent within its owner's holdings and the company's rules, and records each human decision. Proving that each scope is the minimum the work needs is not built yet.
Deciding an agent's authority
| Capability | Status | Page |
|---|---|---|
| Evaluator: checks each requested scope is well formed and in the System Catalog, removes scopes the owner does not hold (rule CEIL-01), applies the agent rules, gives one state per scope | Built | The key join |
| Task Card requirement check (rule CEIL-02): keep only scopes the selected Task Cards need | Partial. The rule is written in the default rule pack. The evaluator does not apply it: it checks only that each Task Card id exists. A requester can ask for any catalogued scope the owner holds | The key join |
| What a Task Card is taken to need | Partial and coarse. The scope lines listed on the Task Card; if none, every catalog scope of the systems it names. A system with no listed scopes gets generic read and update scopes | Task Cards |
| Step-level business capabilities; entitlement mappings validated by application owners | Planned | Task Cards |
| SoD check on the person, the agent alone, and the person plus all their agents | Built | Rule packs and SoD |
| Approval chain: manager, role owner, Internal Controls, IAM; 3 decisions per step | Built | Approval chain |
| Hash-linked ledger with Verify chain; optional server seal | Built | Ledger |
| Agent Authority Record: one view of an agent's purpose, owner, Task Cards, scope calculations, decisions and lifecycle | Planned | Roadmap |
| Human-delegated agents: authority within the named owner's holdings | Built | Holdings |
| Service-owned or department-owned agents with their own authorization model | Not supported. A future consideration | Roadmap |
Running and controlling an issued agent
| Capability | Status | Page |
|---|---|---|
| Gateway check on each routed call: agent status, expiry, issued scope and tool-to-scope match; the credential must match the issued manifest | Built. Only calls routed through the gateway are checked. The business systems behind it are Simulated | Agent gateway |
| Gateway activity record for each routed call | Built | Agent gateway |
| Per-action human approval ("Ask before supervised calls") at the gateway | Not built. The gateway has no approval gate, although the app's runtime table names one. Only a runtime's own approval feature, where one exists, can provide this today | Agent gateway |
| Revoke an issued agent; end an event-bound agent | Built, as manual actions | Request a governed agent |
| Owner departure suspends the owner's agents | Not built. Marking a person as left updates their status, revokes unused invitations and disconnects their phones. Their issued agents and credentials stay active until someone revokes them | Roadmap |
| Re-check issued agents against the owner's current holdings | Planned. The gateway checks the scopes issued at approval, not today's holdings | Roadmap |
| Dependency revalidation when holdings, Task Cards, rules or mappings change | Partial. Manifest freshness (Fresh, Out of date, Broken) and credential expiry are Built. Re-assessing issued agents is Planned | Agent builder and manifests |
Evidence and the company's identity systems
| Capability | Status | Page |
|---|---|---|
| Register and evidence export (CSV and JSON) for agents requested through DutyGraph | Built | Audit evidence |
| Agent inventory reconciliation: match the company's real agent population to governed agents | Planned. The "found outside DutyGraph" identities in the sample are illustrative | Audit evidence |
| Full zip evidence packet with a standalone verifier | Planned | Audit evidence |
| Set up governance for any company (6 packs) | Built | Set up governance |
| Holdings from an uploaded access-export CSV | Built | Holdings |
| Live Okta, Entra, Saviynt and ServiceNow connections | Planned | Integrations |
| Provisioning the agent identity in the company's IAM | Planned; today a "For IAM to do" card. The company's IAM provisions | Request a governed agent |
| Decision Export (the approved decision, sent to IAM or IT service management tools) and Event Import (provisioning, revocation and other events, reconciled with what was approved) | Planned | Integrations |
Run engagements
| Capability | Status | Page |
|---|---|---|
| Accounts, outreach with compliance rules, Inbox | Built | Accounts and Inbox |
| Proposal, Stripe Checkout and invoices, activation by webhook | Built; off until the server has Stripe keys | Engagements and payment |
| Living DutyGraph: scheduler, digests, renewals, client status page | Built | Living DutyGraph |
| DutyGraph Agent: Ask, Review, Edit, Draft an ask | Built; needs an approved AI connection | DutyGraph Agent |
| Phone layouts on every page; advisor web push | Built; push is off until the server has push keys | Phones and notifications |
Connect, trust and security
| Capability | Status | Page |
|---|---|---|
| Advisor MCP server (16 tools) and employee request tools, token sign-in | Built | MCP for advisors, Request from your AI |
| OAuth sign-in for web and mobile AI connectors | Planned | Connect |
| Run tools and run tracking from OpenTelemetry | Planned | Roadmap |
| Tenant, company and participant isolation with forced row-level security | Built | Security and data handling |
| Enterprise SSO and MFA | Planned | Security and data handling |
| Security certifications | None claimed | Security and data handling |
How this page is maintained
- An internal implementation-status register backs this page. Engineers update the register when a capability changes, then update this page to match.
- Each row is checked against the code on the development branch. A row says Built only when the code and its tests exist.
- When a change moves a row, update the Last checked line at the top with the date and commit.
- Other pages link here instead of repeating a status. If you find a page that disagrees with this one, correct that page.
INFO
Status. This page lists every capability with one status. Top-down discovery, opportunities, the agent builder, the evaluator's ceiling and rule checks, SoD checks, the approval chain, the ledger, the gateway check and the evidence export are Built. The Task Card requirement check and dependency revalidation are Partial. The identity and business systems in the samples are Simulated. Pod-down and bottom-up entry, step-level capabilities, owner-departure suspension, per-action approval, reconciliation, Decision Export and Event Import are Planned.
Source: gitbook/product/start-here/built-and-planned.md in the DutyGraph repository.