Weave · Context blueprint
The organizing logic of entity information.
Weave defines the shared vocabulary, categories, and recognized views that make an entity’s information understandable — to its people, its systems, and its agents.
Definitions
- Weave
- The Entity Context Blueprint — a common structure for entity categories, names, and recognized views.
- Entity view
- A structured perspective over living knowledge, such as a business plan, SWOT, risk register, board report, or forecast.
- Living knowledge
- Knowledge that changes as the entity learns — not a frozen document, but a maintained state.
Entity context map
The five surfaces Weave organizes.
01
The Entity
Purpose, values, structure, and continuity.
02
The Served World
Customers, stakeholders, market, and society.
03
The Entity OS
Systems, processes, agents, and workflows.
04
Entity Viability
Financials, obligations, risk, and resilience.
05
Entity Memory
Originals, events, knowledge, and derived views.
Recognized views
Common artifacts, expressed as structured views.
View
Business plan
A composed view over strategy, market, and viability.
View
SWOT
A structured lens over strengths, weaknesses, opportunities, threats.
View
Risk register
A living view of risks, owners, and mitigations.
View
Board report
A recurring narrative over decisions and performance.
View
Financial forecast
A projection built from assumptions and signals.
View
Customer signal map
A rolling view of what customers are telling the entity.
Naming
A shared vocabulary for entity things.
Weave provides consistent naming for people, teams, agents, customers, agreements, obligations, decisions, meetings, financial objects, products, and improvement loops — so both humans and agents refer to the same things by the same names.