The AgentNetwork Framework / Version 2.0

A clearer picture
of the whole company.

Five business layers. Four disciplines that connect them. A practical way to see where people, knowledge, systems and agents fit together.

The 1706 hypothesis, in practice

See the whole system.
Start with the people.

A company map shows where attention goes today. Use it to find the work AI can reliably take on, and the decisions, relationships and creative work that need more of your people.

The five layers connect those choices to ownership, knowledge, systems and evidence. Start with one workflow you can understand properly.

Build your company map ↗
The Company MapFramework 2.0
05
LeadershipHow decisions become direction
04
FunctionsHow the business creates value
03
InfrastructureThe systems that keep work running
02
KnowledgeWhat the organisation knows
01
FoundationPurpose, ownership and decision rights
ContextEvaluationOrchestrationGovernance

Five places to look

The architecture
beneath the activity.

The layers are a useful lens, not a claim that every company should have the same structure. A workflow can cross several layers.

01
Purpose, ownership and decision rights

Foundation

Set the purpose, boundaries and accountability for the business. Establish who can approve investment, grant access, make commitments and accept risk.

Who has the authority to decide and the responsibility to answer for it?

Look for evidence such as:

  • Named accountable owners
  • Decision and escalation rules
  • Approved operating boundaries

Record what is known, what needs checking and who will follow up. An empty answer is more useful than false certainty.

02
What the organisation knows

Knowledge

Connect institutional knowledge with live business context. Retain trusted systems of record, give information an owner and expose only what each workflow needs.

Can the right person or agent find current, trustworthy context?

Look for evidence such as:

  • Current sources with owners
  • Clear access permissions
  • Standards and decision records

Record what is known, what needs checking and who will follow up. An empty answer is more useful than false certainty.

03
The systems that keep work running

Infrastructure

Map systems, integrations and business obligations. Define reliability, operating cost and recovery before handing over consequential work.

What does this capability depend on, and what happens when it fails?

Look for evidence such as:

  • System and dependency inventory
  • Recovery and fallback procedures
  • Operating cost assumptions

Record what is known, what needs checking and who will follow up. An empty answer is more useful than false certainty.

04
How the business creates value

Functions

Map the work that delivers a customer or business outcome. Make the handoffs, exceptions, agent responsibilities and human contributions explicit.

Which workflow would be worth redesigning, and what would improve?

Look for evidence such as:

  • Current and target workflows
  • A measured baseline
  • A named outcome and owner

Record what is known, what needs checking and who will follow up. An empty answer is more useful than false certainty.

05
How decisions become direction

Leadership

Turn evidence into decisions. Review results, resolve tradeoffs and invest in skills and organisational changes that make the new capability useful.

Are we learning from outcomes and changing how we decide?

Look for evidence such as:

  • Review cadence and decision log
  • Outcome measures
  • Training and adoption plan

Record what is known, what needs checking and who will follow up. An empty answer is more useful than false certainty.

Four connecting disciplines

The connections make
the capability work.

Apply these questions to every layer. Consider people, value and operating cost throughout.

01

Context

The right information, current and accessible to the right participants.

02

Evaluation

A definition of good, realistic test cases and an evidence trail.

03

Orchestration

Clear handoffs, dependencies, exceptions and recovery.

04

Governance

Accountability, access, approvals and limits on authority.

Business outcome→Workflow→People & systems→Evidence→Next decision

Methodology / 2.0

Clear assumptions.
Visible evidence.

AgentNetwork is an editorial framework for investigation and design. Its assessments support a conversation; they are not certifications.

What the tools measure

  • Personal capability: six levels describe what you can build and operate. Find your AI level and a practical next exercise.
  • Readiness: Six workflow dimensions are reported separately. Unknown answers remain unknown. There is no aggregate maturity score.
  • Attention: estimates use actual hours and adjustable coverage and review assumptions. The defaults are illustrative.
  • Company Map: counts describe the information recorded. Priorities are chosen by the user.
  • Evidence: labels are self-declared. AgentNetwork does not independently verify a browser assessment.

How evidence is described

LevelMeaning
UnknownThe current state has not been established.
Self-reportedA participant’s account of how work happens.
DocumentedWritten material supports the account.
ObservedThe workflow has been checked in practice.
MeasuredRelevant results have been recorded.

These labels describe a type of evidence. They do not guarantee that it is complete, current or representative.

What changed in version 2.0?
  • Company Map creates an editable, exportable company-specific record.
  • Readiness and autonomy are separate. Governance and human review are part of the design.
  • The Attention Audit uses time inputs and visible assumptions. Unsupported comparison profiles have been removed.
  • Knowledge readiness depends on usability, ownership and access, rather than a particular file format.
  • Playbooks include people, evaluation, operating cost and recovery.
Sources and editorial judgement

The five-layer model, readiness dimensions and operating modes are AgentNetwork’s synthesis. They have not been validated as a statistical benchmark. Primary references inform the implementation guidance:

Reviewed 12 September 2026. Discuss corrections with Craig on LinkedIn.

For practitioners & developers

A framework you
can take with you.

Download the definitions and questions in a structured format. Company maps can be exported separately from the working tool.

Open Company Map

Human-readable.
Agent-readable.

The public framework has a version and stable identifiers. Company Map offers browser tools for reading the current map and plan where supported.

Your private map is not included in the public framework. This version does not offer a hosted MCP server or shared company workspace.

For republication or use in a commercial product, discuss your plans with Craig.