Company Work Map

Open Company Work Map in the sidebar. The first tab shows recorded flows, their tasks, and accountable people. Business-type templates help discovery; they do not create evidence that a company follows a particular process.

Choose Ownership & gaps, AI opportunities, or Work only. These highlights do not move the layout. Click a task to read its inputs, actions, output, software, human decision and evidence. Open its full record to review or change it.

Columns follow recorded dependencies; multiple tasks in a column are branches. The handoff list names the actual source, destination and condition. Visual proximity never establishes a dependency. Connections between flows appear only when an explicit handoff exists. Tasks not yet assigned to a flow remain accessible below the map.

Follow a work item opens an individual recorded case. A case is distinct from its workflow definition and task descriptions. Fictional examples carry their own label. The map does not invent waiting counts, average times or system activity coverage.

Priority to investigate surfaces a recorded constraint hypothesis, not a measured company bottleneck. Inspect its alternative explanation and proposed measurement before presenting a conclusion.

Prepare client readout brings ownership decisions, delay hypotheses and AI scope proposals into a meeting sequence. Review findings with the company, agree an action owner and a measurement window, then use Weekly review and Deliverables to follow through.

Participant confirmation means a task reflects their understanding. Proposed AI scope, company approval and enforced system permissions remain separate. This view does not issue or execute an agent.

Org & duties retains the CSV reporting chart. Relationships and Agents & controls remain available for focused investigations. PostgreSQL remains authoritative; Neo4j remains a derived relationship projection. The Work Map can display workspace records even when the graph connection is unavailable.