Bow Tie Kreative Intel System

File 01

The LAKA grammar

Four connected layers, not one flat grid. States say how deep a change goes, internal variables say what part of the system it touches, change variables say how it behaves over time, and the execution lens says what you are allowed to do about it.

The canonical protocol

Every run walks the same seven stages. Elimination is recorded, not hidden — a discarded option with its reason is evidence too.

Canonical protocol
StagePurposeRequired output
SymptomRecord the visible signal without diagnosing itneutral observation and source
DecompositionSeparate system componentsobjects, conditions, actions, tools, resources, stakeholders, dependencies, outcomes
VarietyGenerate materially different explanations and interventionsmorphological alternatives, including do-nothing and measurement-first
EliminationFilter without hiding discarded optionsdecision table using evidence, fit, urgency, reversibility, cost, capacity, risk, and time-to-evidence
PrescriptionSelect the smallest sufficient interventionaction, owner, inputs, expected state change, stop rule
RoutingSend work to the correct human/tool/agentroute, authorization, data classification, review gate
ReviewCompare predicted and observed outcomesresult, variance, learning, next state

Source: file 00 · 2-canonical-protocol · line 23

Five change states

Five change states
CodeStateMeaningAudit question
C0BaselineCurrent/default state; no meaningful changeWhat exists now and how does it normally behave?
C1Minor ChangeLocal, low-depth adjustment; limited dependenciesWhat can improve through tuning or one-step repair?
C2Major ChangeMaterial change across several components or outcomesWhat requires coordinated redesign or meaningful investment?
C3Structural ChangeRules, architecture, incentives, ownership, or feedback loops changeWhat must be rebuilt at the system level?
C4Paradigm ChangeUnit of value, category, business model, or governing assumption changesWhat new demand curve makes the old comparison less relevant?

Source: file 01 · layer-a-change-states · line 9

Ten internal system variables

Ten internal system variables
CodeVariableDefinitionDiagnostic prompt
S1ObjectWhat is acted uponWhat entity, asset, message, process, or relationship changes?
S2ConditionsOperating circumstancesUnder what market, technical, temporal, geographic, or regulatory conditions?
S3ActionsWhat the system doesWhat actions create, move, transform, measure, or stop value?
S4ToolsMechanismsWhich human, software, channel, model, contract, or machine performs the action?
S5ResourcesRequired inputsWhat information, people, capital, energy, permission, time, or assets are needed?
S6OutcomesProduced statesWhat measurable output or outcome results?
S7FeedbackLearning and controlHow does the result change the next decision or system state?
S8ConstraintsLimitsWhat limits performance, legality, adoption, reliability, or scale?
S9ValueBeneficiary and benefitFor whom is value created, of what type, and at whose cost?
S10Failure ModeBreakdownHow does the system fail, become misleading, or create harm at this state?

Source: file 01 · layer-b-internal-system-variables · line 21

Fourteen change variables

Fourteen change variables
CodeVariableCore questionUseful measures
D1MagnitudeHow much change?absolute delta, percentage delta, severity
D2RateHow quickly?change per day/week/quarter
D3DirectionMoving toward what?improving, degrading, diverging, converging
D4ScopeHow broadly?entities, teams, regions, products, channels affected
D5DepthHow fundamentally?surface symptom through governing rule
D6DurationFor how long?transient, seasonal, persistent, permanent
D7FrequencyHow often?event count per period
D8AccelerationIs the rate changing?second difference, slope change
D9VariabilityHow consistent or unpredictable?range, variance, coefficient of variation
D10DetectabilityHow visible or measurable?signal latency, observability, false-negative risk
D11ReversibilityCan it be undone?recovery time, switching cost, data persistence
D12PropagationHow does it spread?dependency paths, affected nodes, time to spread
D13AmplificationWhat increases or dampens it?multipliers, network effects, feedback gain
D14AccumulationWhat builds over time?backlog, technical debt, reputation memory, compounding value

Source: file 01 · layer-c-fourteen-change-variables · line 38

Six execution-impact states

In passive research most valid collection actions stay in I1–I2. I3 produces the audit artifact, I4 needs explicit authorization, and I5–I6 are not prospecting tools at all.

I1

Read-only

Public-source retrieval and passive observation; default allowed

I2

Verify

Recheck, corroborate, calculate, or reproduce without changing target state; default allowed

I3

Local change

Create local notes, models, reports, and exports; allowed within project scope

I4

Remote/persistent change

Save externally, update CRM, post, email, or mutate remote history; explicit authorization and human review required

I5

Destructive change

Delete, overwrite, mass-contact, disrupt, exploit, or irreversibly alter; blocked unless separately and explicitly authorized for a legitimate administrative task

I6

Security/policy boundary

Authentication, credentials, protected systems, sensitive data, policy exceptions; stop and route to an authorized specialist

Source: file 01 · execution-impact · line 69

Expand the 216-lens cube →

Grammar operators

Grammar operators
SymbolMeaningExample
+compose required partsClaim + Evidence + Time
×generate combinationsChannel × Persona × Funnel Stage
state transitionmanual intake → instrumented intake
|mutually exclusive alternativesObserved | Inferred | Unknown
?optional only when justifiedExecutive?
{…}repeat zero or more{Evidence}
[…]gate or constraint[E3+ required]
~inference, never direct factslow response ~ queue friction
!contradiction or stop! recipient unresolved
@source/provenance pointer@source-0042
$[L,B,H]low/base/high financial range$[25k,60k,140k]
Δmeasured changeΔSOV = current − prior

Source: file 01 · 2-operators · line 82

The fifty-cell structural matrix

Ten internal variables against five change states. The cell is the prompt: what does this variable look like at this depth of change?

Fifty-cell structural matrix
VariableC0 BaselineC1 MinorC2 MajorC3 StructuralC4 Paradigm
Objectcurrent unitlocally adjusted unitmaterially redesigned unitrelationships/rules become the objectunit of value/category changes
Conditionsnormal operating contextone bounded condition changesseveral important conditions changegoverning conditions are redesignedold conditions become irrelevant or inverted
Actionscurrent workflowtune/repair one actioncoordinate new action setchange decision rights and feedbackintroduce a new value-producing behavior
Toolsincumbent toolsconfigure/augmentreplace/integrate a major toolsetredesign architecture/tool ownershiptool becomes a new platform or market mechanism
Resourcescurrent inputssmall incremental inputmeaningful new capacityreallocate capital/people/data rightsresource model changes or new resource is created
Outcomescurrent resultlocal KPI liftmaterial multi-KPI changedurable system performance changenew category outcome/demand curve
Feedbackcurrent reportingadd a signal/alertclosed-loop experimentationfeedback changes governance/incentiveslearning system continuously redefines value
Constraintscurrent limitsremove one frictionovercome a material bottleneckchange policy/architecture/incentive constraintconstraint becomes advantage or disappears
Valuecurrent beneficiary/valuemore of same valuenew value mix or segmentvalue distribution changesnew beneficiary or unit of value
Failure Modecurrent breakdownlocal side effectcoordination/capacity failuresystemic lock-in or transition failurecategory error, adoption discontinuity, new externality

Source: file 01 · 5-fifty-cell-structural-matrix · line 171