Glossary and quick reference
The file states (Confirmed, Observed, Inferred, Disputed, Unknown, Proposed, Slot, Generated) describe Company Repo files. The classification labels (Known, Inferred, Assumed, Missing) describe the basis of a work record.
| Term | Meaning in this application |
|---|---|
| Accepted source | Source reviewed for use; acceptance does not prove every assertion |
| Accountable owner | Person named as accountable for the described task or claim |
| Advisor draft | Notes text the advisor accepted from a Copilot Edit. It shows in the file as "not confirmed by <Company>" and the file stays Inferred |
| Advisor review | Recorded human assessment of a record’s current completeness or meaning |
| Agent proposal | Draft assistance design bound to work versions, with no operative grant |
| Anchor | The person, file or department that the Copilot's chain starts from. The panel shows "Anchored on: <name>". Select × to clear it |
| Answer | What a person sends back for an ask |
| Ask | A question set that DutyGraph sends to a person. A queued ask is an unsent draft in Discovery › Asks |
| Authority | Legitimate permission to act in a business context; separate from work description |
| Automation candidate | A Task Card with a proposed AI mode. It is not an approved agent |
| Binding | Reference to an exact record version and hash used by another artifact |
| Case | One persisted instance of a reviewed manual workflow |
| Chain | The files above, below and across from the anchor: strategy, initiatives, mandate, role, duties, Task Cards, runbooks and handoffs. The Copilot reads it |
| Classification | Known, Inferred, Assumed or Missing label describing the stated basis |
| Company brief | The generated file company/brief.md: status, initiatives, work in motion, the last 14 days, key people and top gaps. Every Copilot request carries it |
| Company Repo | The company as a tree of Markdown files, compiled from the database, each with a state and sources. Not a second store |
| Company revision | Incrementing value identifying changes to the company’s record |
| Company Snapshot | The company's front page (Overview). It can be printed or saved as a PDF |
| Composer | The Discovery page that edits an ask's questions and email wording and shows the real email |
| Confirmation | A named participant’s decision about an exact task version/hash, later accepted by advisor |
| Confirmed (file state) | A person at the company confirmed it in DutyGraph. Recorded, not signed |
| Constraint hypothesis | Testable explanation of what may limit overall output |
| Copilot | The Repo Copilot: a panel that answers, reviews, proposes edits and drafts asks. It only proposes |
| Coverage | Explicit scope of roster, responses, tasks, observations or audit activity |
| Discriminator | Observation or test intended to distinguish competing explanations |
| Disputed | Sources or people disagree |
| Duty | Continuing responsibility that may contain several tasks |
| Evidence origin | Identity of the original source, used to avoid counting copies as independent |
| Execution mode | The mode of a workflow file: people only, people and agents, or agents only. It comes from the proposed modes of its Task Cards. It does not approve an agent |
| Export | Frozen internal record package; distinct from a reviewed client report |
| Focused review | A Copilot review of one To review finding that ends in a verdict: confirm, correct or ask a person |
| Framework | An evidence-bound analysis with defined upstream prerequisites |
| Generated (file state) | A file DutyGraph builds from other files, such as an index or the company brief |
| Guardrail | Condition that must remain acceptable while testing a change |
| Handoff | Contract describing what the receiving task requires and how exceptions are handled |
| Handoff file | A Repo file in flows/handoffs/ for one handoff: from and to task and department, what is handed over, the time limit and the failure action |
| Hash | Digest of canonical content or file bytes; not an approval signature |
| Human checkpoint | Described point where a person must review or decide |
| Human-verified fact | A fact a person at the company, or the advisor, confirmed or corrected. New research cannot outvote it |
| Idempotency | Retrying the same command key/content returns its prior result instead of repeating it |
| Inferred (file state) | Research or the advisor suggests it. Nobody at the company confirmed it |
| Initiative | A goal that leadership works toward. A Repo file in company/initiatives/, from an accepted priorities or goals answer, the engagement outcome or the company goal. It serves the strategy |
| Intervention | Proposed change with owner, prediction, measure, stop conditions and review date |
| Keep research current | The switch on the Company Research step page that refreshes due files on a schedule, within the monthly cap. Off by default |
| Layer | One level of the company's operating model on the Repo's Layer row: Company & market, Leadership, Departments, Team, Work. Each file states it in the layer key of its frontmatter |
| Link | A relation between 2 Repo files, up (serves, owned by), down (duties, Task Cards) or across (handoffs, workflows). DutyGraph computes it from records. Details lists it under LINKS |
| Locator | Reference precise enough to find the supporting passage or observation |
| Mandate | What leadership asks a department to deliver: the initiatives it serves. The Mandate section of the department charter |
| Manual case observation | Advisor’s record of human work, not independent evidence of external execution |
| Monthly cap | The most that scheduled refreshes can spend in one calendar month. At the cap, scheduled refreshes stop until the next month. Refresh now does not count |
| Notes | Versioned advisor content for a Repo file (migration 0043). Every version is kept |
| Observed | A client source supports the file |
| Outcome review | Interpretation against a preserved prediction and measurement snapshot |
| Performer | Person described as carrying out a task |
| Point of contact | The client person who receives the first touch |
| Private link | A bearer link to an answer page for one named person. It opens without an account |
| Projection | Rebuildable graph metadata derived from authoritative records |
| Proposed link | A link that a proposed record or an inference states. Nobody confirmed it. Details shows "Proposed", and the Copilot's path shows it dashed |
| Proposed mode | The AI mode written on a Task Card. A proposal, not a permission |
| Refresh plan | The research plan for a file that changes over time: what changes, how often, the fields and the sources. It is the refresh: block in the file's frontmatter |
| Report audience | Explicit intended recipients whose names are frozen into a client packet |
| Roster | People in the bounded engagement; not necessarily the entire company |
| Slot | A Repo file that nothing has filled yet |
| Source retraction | Removal of a source from current use while preserving history and marking dependencies stale |
| Stale | A record needs fresh review because its inputs, content or review period changed |
| Task | Bounded trigger-to-output work description |
| Task Card | One recorded task with its trigger, steps, inputs and outputs |
| Team list | The names and roles of the people who do the work |
| Tenant | Application isolation boundary for an account’s company data |
| Throughput | Completed system output per period, defined for the engagement |
| To review | The Repo tab with answers, proposed work and research findings that need a decision |
| Workflow | Reviewed sequence and branches of tasks and receiving handoffs |
Before clicking Review
Check the current version, required fields, evidence, accountable people, unresolved conflicts, and scope. State why the review is justified. If the source changed, refresh the derived record before reviewing it.
Before saying Confirmed
Check that both required roles have accepted correct decisions for the current version and hash. Check the review date. Do not transfer a past confirmation to a new description.
Before saying Improved
Check the formula, cohort, source, baseline, observation window, target and confounders. Distinguish arithmetic movement from causal attribution. If the source is synthetic, say so.
Before saying Authorized or Deployed
The current local build does not establish either state for external business systems. A draft task, reviewed diagnosis, report approval or exported agent package does not change that. Consult the separate integration and production acceptance plan.
Before sending a client packet
Check audience, exact content, current bindings, exclusions, and limitations. Download the reviewed packet, inspect it and use the agreed channel. Keep a distribution record; the application does not send messages or recall downloaded copies.
Before you queue an ask
Read every question. Each question asks about one missing, unconfirmed or disputed item. It names the person who can answer and quotes the current value. Do not ask about a confirmed value. Queuing does not send anything. Send from the composer after you read the real email.
Before you accept a Copilot proposal
Read the diff and the Notes preview. Check the label: a best guess from common practice is not a fact about the company. Accept writes an advisor entry. The file stays Inferred until a person at the company confirms it.