pattern.01 · intuitive launch
The founder starts from skill and conviction
Hidden issue: the opportunity was never translated into system design.
V-Frame
Methodology you can execute.
V-Frame is the Business Engineering methodology behind Entvex — the operating language of the practice: nine variables across Discovery, Proof and Scale, with typed transitions, artifacts and quality gates — specified precisely enough to be run by founders, consultants and AI agents against the same definitions.
business engineering · methodology-as-code · white paper v0.14
- Vista
- Vector
- Venture
- Verity
- Value
- Viability
- Velocity
- Vertex
- Vow
A business is not an activity. It is a designed system capable of scaling.
The problem V-Frame solves
Knowledge is abundant. Application is the constraint.
Businesses plateau because the work was built as activity, not architecture. And in the AI era, anyone can generate a strategy in minutes — the harder questions are which knowledge applies, what context is missing, which artifact to produce, and when a decision is actually ready.
pattern.02 · operational comfort
Revenue stabilizes. The business feels real
Hidden issue: the founder becomes the operating system. Processes, roles and decisions stay informal.
pattern.03 · the ceiling
Growth attempts create stress, mistakes, overload
Hidden issue: the architecture can’t absorb complexity.
The plateau isn’t a moral failure — it’s a structural outcome.
The AI-era gap
entvex diagnose --ai-era
knowledge access universal
frameworks & templates abundant
fluent AI output instant
which knowledge applies unresolved
what context is missing invisible
which artifact to produce undefined
when a decision is ready ungoverned
The gap is not access to intelligence — it’s the structured application of it.
Adaptive autonomy doctrine
The model reasons. The methodology governs. The human decides.
V-Frame defines the Business Execution Contract — case context, role, route, artifact, sources, quality gate. The AI agent owns the reasoning path within it. Strategic choices, commitments and risk acceptance remain human responsibilities.
The nine variables
Nine variables. Three phases. One grid.
Read it sequentially as stages, diagnostically as a 3×3 architecture, or configurably as a molecular model. Select a variable — each is typed: entry conditions, outputs, exit condition, failure mode — and the eight transitions between them are type-checked.
phase 1 · discovery What should we do?
phase 2 · proof Does it work?
phase 3 · scale How do we sustain it?
discovery · 01 Vista Scan & commit
What deserves attention?
Identify a meaningful opportunity and confirm real conviction before resources are committed.
example outputs
Opportunity MapConviction Statement
Illustrative, not exhaustive — the actual artifacts are configured per case from the V-Frame library of roles, workflows, skills and artifacts.
Entry: Access to market signals, time for sustained reflection, willingness to drop non-converging opportunities.
Exit condition: Signal evidence from at least three of the four sources, resources committed, and a commitment the founder can state to a third party without ambiguity.
fail.mode: Confusing trend-following with opportunity identification — “it’s popular right now” is not Vista.
discovery · 02 Vector Align & exclude
Which path are we choosing?
Convert an opportunity into strategic direction by choosing one path — and explicitly excluding the competing ones.
example outputs
Strategic BriefResource Allocation Plan
Illustrative, not exhaustive — the actual artifacts are configured per case from the V-Frame library of roles, workflows, skills and artifacts.
Entry: Vista’s Opportunity Map, an honest resource assessment, willingness to make exclusionary commitments.
Exit condition: One direction documented with rationale, at least three alternatives explicitly excluded with reasons, resources withdrawn from competing initiatives.
fail.mode: Keeping several options open until none receives enough force.
discovery · 03 Venture Prototype & deploy
What must be tested in reality?
Build the smallest credible version of the idea and deploy it in real conditions to test the core assumption.
example outputs
Pilot Design DocumentMVP / First Deployable VersionPilot Engagement Plan
Illustrative, not exhaustive — the actual artifacts are configured per case from the V-Frame library of roles, workflows, skills and artifacts.
Entry: The Strategic Brief, one identified core hypothesis, minimum resources for a meaningful test.
Exit condition: A falsifiable core hypothesis with numeric success and failure metrics defined before deployment — deployed with real customers, within a predefined resource limit.
fail.mode: Building too much before evidence exists — or experimenting without success criteria.
proof · 04 Verity Measure & conclude
What did the evidence say?
Measure results against predefined criteria and produce an honest verdict on what is true, false or unresolved.
example outputs
Hypothesis ScorecardVerdict Brief
Illustrative, not exhaustive — the actual artifacts are configured per case from the V-Frame library of roles, workflows, skills and artifacts.
Entry: A completed pilot with measurement in place, pre-defined metrics, willingness to accept the verdict.
Exit condition: Critical hypotheses have written verdicts, ambiguous findings are classified, implications are accepted.
fail.mode: Explaining weak evidence away because the team wants the idea to work.
proof · 05 Value Prove & articulate
Why would the customer pay?
Prove that the offering creates recognizable value — and express it in language the customer actually uses.
example outputs
Validated Value PropositionCustomer Voice DocumentPricing Validation Record
Illustrative, not exhaustive — the actual artifacts are configured per case from the V-Frame library of roles, workflows, skills and artifacts.
Entry: Confirmed hypotheses from Verity, access to actual customers — not prospects or proxies.
Exit condition: The proposition fits one sentence, a segment shows voluntary repeat willingness to pay in aligned terms — and the offering isn’t surviving on inertia or absence of alternatives.
fail.mode: Treating internal belief as proof of value.
proof · 06 Viability Stress-test & prepare
Can the system withstand scale?
Stress-test economics, processes and team capacity before pursuing growth.
example outputs
Operations Readiness AssessmentProcess DocumentationUnit Economics Model
Illustrative, not exhaustive — the actual artifacts are configured per case from the V-Frame library of roles, workflows, skills and artifacts.
Entry: A validated value proposition, current operational data, an honest projection of expected scale.
Exit condition: Economics stay positive at projected scale, core processes are documented, team roles have clear owners, and one full cycle runs without founder execution.
fail.mode: Scaling a valuable offer on an operating model that can’t absorb demand.
scale · 07 Velocity Accelerate & scale
Which growth engine compounds?
Activate self-reinforcing mechanisms that grow the business without a proportional increase in founder time.
example outputs
Growth Engine BlueprintGrowth Metrics DashboardChannel Performance Record
Illustrative, not exhaustive — the actual artifacts are configured per case from the V-Frame library of roles, workflows, skills and artifacts.
Entry: Operational readiness from Viability, candidate growth mechanisms, measurable acquisition cost and lifetime value.
Exit condition: At least one growth mechanism feeds the next cycle, acquisition efficiency improves, founder dependency decreases.
fail.mode: Confusing more effort, more spending or more hours with scalable growth.
scale · 08 Vertex Differentiate & defend
What makes the position hard to copy?
Build a defensible position through interconnected advantages — not one isolated strength.
example outputs
Moat Architecture DocumentCompetitive Defense Plan
Illustrative, not exhaustive — the actual artifacts are configured per case from the V-Frame library of roles, workflows, skills and artifacts.
Entry: A functioning growth engine, a clear read of the competitive landscape.
Exit condition: At least three interconnected advantages that would take a well-funded competitor 18+ months to replicate in combination — actively maintained as a system.
fail.mode: Believing brand, relationships or low price alone is a durable moat.
scale · 09 Vow Pledge & govern
What commitments now bind the system?
Convert achieved value into explicit obligations — across customers, brand, contracts and internal operations.
example outputs
Commitment FrameworkGovernance PlanPublic Commitment Statement
Illustrative, not exhaustive — the actual artifacts are configured per case from the V-Frame library of roles, workflows, skills and artifacts.
Entry: A defended position from Vertex, clarity on which commitments the business can bear and enforce.
Exit condition: Commitments exist in writing at all four levels — customer, brand, contractual, internal — alignment across levels is verified, governance routines run, and the business accepts formal accountability for non-delivery.
fail.mode: Making public promises the operating system can’t reliably keep.
Modes of use
One grid, three ways to read it.
Delivered in three forms — a conceptual methodology, a practitioner-guided consulting system, an AI-assisted navigation system — and engaged through three modes of use:
mode: sequence
Sequence
Learn and run the full path from Vista to Vow. Best when building from zero, teaching the method, or orienting a new practitioner.
mode: architecture
3×3 Diagnostic
Read an existing organization through the grid: locate the active variable, the skipped stages, the systemic weakness.
mode: molecular
Configuration
Activate selected variables for a specific challenge — disciplined composition, not random selection. Pairs with Lab, Engine and Hybrid contexts.
Canonical configurations
Activate only what the situation needs.
An existing business rarely needs all nine variables at once — most engagements activate three to five elements. A configuration operates on existing business state: unactivated variables aren’t skipped, they already exist as state from prior cycles. Inputs checked, transitions explicit, outputs quality-gated.
config: strategic-refresh
Strategic Refresh
A renewed direction with explicit exclusions and governance commitments — for a business that has drifted.
VistaVectorVow
config: scaling-crisis
Scaling Crisis
A stronger operating model and growth engine that can absorb scale — when demand exists but delivery and economics are under stress.
ValueViabilityVelocity
config: defensible-position
Defensible Position
A moat architecture and commitment system that reinforce each other — for a business with traction to protect.
VertexVow
Original contribution
What’s actually new here.
V-Frame doesn’t invent business design from nothing. It reorganizes proven management knowledge into a structured, executable system — through five architectural moves.
01 · Readiness, not enthusiasm
Most methods describe stages. V-Frame defines what must be true before the next stage is allowed — advancement runs on evidence, not on confidence or the calendar.
02 · Commitment gets its own architecture
Businesses grow through informal promises until they become liabilities. Vow makes commitments explicit — customer, brand, contractual and internal — and turns them into governed obligations.
03 · Cycles start when reality changes
Not calendar-driven loops. A new cycle begins when the business state shifts — readiness to scale, a broken promise, a changed market — and re-entry can target a single variable.
04 · Composable, not rigid
Full sequence, diagnostic matrix or selected elements — variables combine only when the problem requires it and the required inputs exist.
05 · Same logic, any size
From a solo expert to a mid-size organization: the variable stays the same, only artifact depth and governance intensity change. Enterprise discipline, right-sized.
Intellectual lineage
Navigation, not replacement.
V-Frame doesn’t compete with established frameworks. It routes the business situation to the knowledge that applies — loaded as governed Knowledge Packs, with sources, applicability rules and quality criteria.
LeanPorterJobs-to-be-DoneCynefinDesign ThinkingTheory of ConstraintsFlywheel & Growth LoopsCompetitive Advantage TheoryAgilePMIITILCOBITTOGAFSix SigmaISO 9001ISO 27001ISO 31000
A small sample, not the full set — V-Frame draws on a much larger body of methods, and the entry situation decides which Knowledge Packs actually load.
Agent-executable business engineering
Built for the AI runtime.
Projects, Skills, MCP and agents are runtime components. V-Frame is the layer above them — it decides what to do, in which order, with which sources, producing which artifact and passing which gate. Without it, the runtime is fast but blind.
layer.workspaceProjectwhere work is organized
layer.capabilitySkillshow a task is performed
layer.accessMCPhow systems are reached
layer.executionAgentswho performs the work
layer.governingV-Framewhy, when, with what proof
The runtime loop
One case, five governed moves.
vframe run --case
load case snapshot, not 500 files
select role · workflow · knowledge pack
execute skills draft the artifact
review quality gate · maker-checker
commit decision log · state update
repository = memory · LLM = reasoning engine · human = decision authority
How a case is routed
From business intent to the next step — every link governed.
the navigation chain
business intentstructured diagnosismethodology mappingrole selectionknowledge selectionartifact generationquality gatedecision lognext step
the business engineering reference system
business needengagement scenariocapability areaintervention patternartifacts · roles · skills · workflows · gates · knowledgecase execution plan
// engagement operating layer: diagnostic cards route the intake · engagement memory keeps the reasoning trail — decisions, assumptions, risks, open questions · case management stores the engagement · adaptive autonomy is the operating contract
// doctrine: workflows are recommended routes, not rails · quality gates judge business validity, not procedural compliance · prompts stay lean — the methodology lives in the repository, not the prompt
The north star
One system. Three faces.
Mature V-Frame is not a document set or an AI assistant. It is a methodological operating system for consulting, venture creation and business engineering — three things at once:
face.01 · methodology
How to think
Business context → diagnosis → direction → artifacts → actions → evidence → learning → reusable patterns.
face.02 · case operating system
How a case lives
Sources registered, decisions logged, artifacts promoted from draft to approved, deliverables governed — and reusable next time.
face.03 · ai execution framework
How agents are governed
Which agent, which role, which workflow, which sources, which artifact, which gate, what needs approval, how memory updates.
Who runs it: consulting firms · venture studios · portfolio founders · transformation teams · AI agencies.
ent + {v₁ … v₉} → ex
Put your business through the frame.
Start with a Diagnostic Sprint — locate the active variable and the real constraint. Or bring your team into V-Frame Enablement and run the methodology yourselves.
entvex.com/en/connect · white paper v0.14 available on request