AI-Native Business Function Analysis
Uppercase folder name is intentional: this is a private .FLOW operating surface.
This workchart analyses business units using the Tight Five, then applies optional AI-native, crypto-rail, and OaaS lenses. Goal: standard work that compounds quality — define the current best-known method, follow it, measure it, then improve the standard before the next run.
Standardized Protocol
Develop standardized practices, patterns and process for the analysis of core business functions using the 5P framework.
- Performance: KPIs what does good and bad benchmark look like?
- Principles: How is value created, and distributed.
- Platform: What assets, tools, tech needed?
- Process: How is work done, what workflows, tools, knowledge & skills needed? Required Outcomes and AI Delegation Risk.
- Players: What are key roles, accountable outcomes and relationships. HiTL capabilities
Canonical 5P Source
BUSINESS-UNIT-ANALYSIS and industry-analysis inherit from one canonical 5P spec. On conflict, the spec wins.
- Canonical 5P spec (SSOT):
.FLOW/LOOPS/_OUTPUT-PATTERNS/business/5p-canonical-spec.md - Registry:
.FLOW/LOOPS/_GAUGES/registries/5p/index.md - Doctrinal anchor: Tight Five matrix
Changes to the canonical spec must cascade to this flow, industry-analysis, and all 5P dimension skills in the same commit.
Connection Model
flow.json is the active spine. It owns orchestration only: phase order, gates, module bindings, execution order, kill signals, and path tokens.
Reusable recipes live in _MODULES/5p-analysis/**/task.json. Do not add inline inputs, outputs, checks, or kill_signals to flow.json tasks.
Do not add task recipe files under this folder. Per the LOCKED connection model (_MODULES/module-blueprint.md), flow.json is orchestration only — each task is a pure connection { id, name, module, module_params } and module_params.mode selects the Module mode. The recipe — inputs, outputs, checks, kill_signals — lives in the Module task.json (multi-mode Modules use a modes map). If work is reusable, define or update a Module. If artifact shape is reusable, put it under _OUTPUT-PATTERNS. If measurement is reusable, put it under _GAUGES.
Relationship to Industry Analysis
| Industry Analysis | Business Unit Analysis | |
|---|---|---|
| Scope | Industry (payments, healthspan...) | Function or unit (finance, marketing, sales, ops...) |
| Output | docs/industries/{industry}/ until migrated | playbook/business/.../{unit}/ or another declared playbook/ output root |
| Principles | First principles, data flow, nomenclature | Value creation, essential data, glossary |
| Performance | Metrics, KPIs, friction map | What good looks like, warnings, decision flows |
| Platform | ABCD tech, disruption wedge | Best stack + essential stack by growth stage |
| Process | Workflows, methods | Workflow + tools/knowledge/skills → full workchart |
| Players | Ecosystem, human/AI | Employees, suppliers, partners, customers |
5P Output Structure
playbook/{declared-output-root}/
├── index.mdx (navigation front door; route before detail)
├── principles.mdx (what guides the function)
├── performance.mdx (what proves it works)
├── platform/ (what tools and data it runs on)
├── process/ (how the work runs)
└── players/ or positions/ (who participates; legacy function pages may keep positions)
The index.mdx page is a navigation surface, not a detail page. Lens detail from AI-native readiness, crypto-rail leverage, or OaaS priority belongs in the relevant 5P child surface unless the index only summarizes and routes.
Phases
| Phase | Purpose | Quality Gate |
|---|---|---|
| SCAFFOLD | Confirm the declared 5P surface | Output root, current files, stale paths, and dimension mapping explicit |
| ORIENT | Ground the unit | Research corpus and 5P audit table exist |
| ANALYZE | Map value, data, and decisions | Canonical 5P brief plus AI-native readiness score |
| LEVERAGE | Test crypto-rail fit | Each recommendation names a measurable lever, risk, and not-applicable verdict where relevant |
| PRIORITIZE | Rank OaaS/build decisions | Need-value, delivery quality, AI readiness, crypto leverage, strategic leverage, and engineering state scored with rationale |
| PUBLISH | Update the 5P surface | Published pages carry the canonical analysis plus active lenses without leaking run scaffolding |
| CLOSE | Validate, register, improve | Validation report, registry row, benchmark reading, and standard-work improvement exist |
Content Definitions
The content authority is .FLOW/LOOPS/_OUTPUT-PATTERNS/business/5p-canonical-spec.md. This section is only a routing reminder.
- Principles: value creation statement, essential data list, glossary, decisions data drives.
- Performance: good/bad pairs, warning signals, alerts with owner, decision flows ending in action.
- Platform: best stack, essential stack by growth stage, data assets, capital assets where applicable.
- Process: executable workflow, capability map, tools/knowledge/skills, decision points.
- Players / Positions: participants, roles filled, hand-off contracts, human/AI split, coordination, failure modes.
Files
| File | Purpose |
|---|---|
flow.json | Active module-bound orchestration spine |
CLAUDE.md | Local operating contract for this workchart |
No local workflow-tasks/, benchmarks/, template.json, schema.json, output-paths.json, local run examples, or _runs/. Runtime scratch output belongs under .FLOW/LOOPS/_RUNS/BUSINESS-UNIT-ANALYSIS/{run_id}/. Reusable measurements belong under .FLOW/LOOPS/_GAUGES/**.
Skills
- ops-audit-principles — Principles dimension.
- ops-audit-performance — Performance dimension.
- ops-audit-platform — Platform dimension.
- ops-audit-process — Process dimension.
- ops-run-players — Players / positions dimension.
Connection
.FLOW/LOOPS/ANALYSE-INDUSTRY/CLAUDE.md— same module-bound 5P pattern at industry scope..FLOW/LOOPS/_GAUGES/workchart-benchmarks/business-unit-analysis.md— reliability benchmark for this workchart..FLOW/LOOPS/_GAUGES/registries/5p/schema.md— registry row contract emitted at CLOSE.