Situation
Identify the event, tension or decision that activates the system.
BomRuntime™
An operating system that carries decisions into daily work and maintains quality over time.
OPERATE
01 / HOW TO USEBom Runtime™ / OPERATE
The playbook leads from the situation to transfer.
The document supports scope preparation, system accountability and verification of material completeness before the next layer assumes the work.
Entry contract
Confirm the source material, decision owner, people required for the process and stated outcome.
Accountability layers
Run each layer as a distinct analytical and operating function with its own outcome.
Transfer
Verify the artefacts, decision status, conditions for assuming the work and the system accountable for the next scope.
00 / CONTENTSBom Runtime™ / OPERATE
A map of functions, material and accountability.
Each layer remains distinct: it addresses a different type of decision, outcome and condition for further use.
02 / DEFINITION AND ROLEOPERATE
Quality is culture. Culture is a system.
Bom Runtime™ translates business architecture into roles, accountabilities, processes, checklists, quality standards, one source of truth, onboarding and context ready for work with AI.
02.1 / OPERATING DEFINITIONBom Runtime™ / OPERATE
Roles, rhythm, quality standards and knowledge create a repeatable way of operating.
Bom Runtime™ maintains the system's logic, rhythm and quality over time.
The Maintain layer governs sources, governing versions, quality standards and the update cycle. The Operate layer translates company logic into workflows, roles, accountabilities and tools for daily work.
The system establishes conditions in which decisions remain accessible, work has completion criteria, knowledge moves between people and AI context is updated under human control.
03 / ENTRY CONDITIONSBom Runtime™ / OPERATE
The engagement contract defines the material, mandate and outcome.
The scope follows from the weight of the decision, organisational readiness and the quality of the source material.
Activation situations
- a structured strategy, offer or business model
- growth in the team, number of projects or touchpoints
- operating knowledge dispersed across people, documents and tools
- preparation of AI, automation or a work-management system
Input material
- decisions and architecture from Bom Blueprint™
- current roles, processes, tools and rituals
- operating knowledge and quality criteria
Engagement outcome
- an operating accountability map
- working rituals, checklists, SOPs and Definition of Done
- knowledge-repository structure and direction for automation and AI
04 / ENTRY SITUATIONSBom Runtime™ / OPERATE
The situation leads to a proportionate outcome.
Each situation indicates a different decision weight, source material and scope of system accountability.
The architecture exists and work returns to former habits
Decisions are documented and daily practice diverges from the agreed principles.
OUTCOMEA review rhythm and workflow aligned with the documented logic.
Document versions are multiplying
The team works with several variants of the same material at the same time.
OUTCOMEOne governing source with a register of statuses and owners.
The owner remains involved in every decision
Decisions return to one person because the principles exist in that person's memory.
OUTCOMERoles, accountabilities and decision criteria recorded in the system.
The organisation is implementing AI tools
Work with agents requires current context and clear accountability.
OUTCOMEAI context with usage principles and decision ownership.
05 / SYSTEM MODELBom Runtime™ / OPERATE
Accountability layers.
Each element retains its own analytical and operating function and transfers a defined outcome.
Role
Roles, decision owners, the RACI model and escalation principles.
Rhythm
Weekly, monthly and quarterly rituals that maintain direction and priorities.
Source
One source of truth for knowledge, documentation, decisions and materials.
Quality
Checklists, Definition of Done and work-acceptance principles.
Transfer
Onboarding, instructions and assumption of context by people and partners.
AI context
Knowledge and processes ready for workflows, prompts, integrations and automation.
06 / OPERATING LOGICBom Runtime™ / OPERATE
Operating logic.
The sequence structures the dependencies between source material, development, decision and further use.
Decision
Each key area of work has an owner, decision criterion and escalation route.
Rhythm
The week, month and quarter structure priorities, quality review and information exchange.
Standard
Checklists, SOPs and Definition of Done describe complete, ready-to-use work.
Knowledge
The knowledge base and onboarding prepare the team, partners and AI workflows.
07 / SCOPE OF RESPONSIBILITYBom Runtime™ / OPERATE
The scope defines the functions governed by the system.
The system boundary follows from the type of decision and the outcome to be assumed by the organisation or the next Bom Dia Creation™ layer.
Scope of work
- roles, accountabilities and decision model
- operating processes and quality standards
- weekly, monthly and quarterly rhythm
- one source of truth and a knowledge base
- onboarding and knowledge transfer
- readiness for work with AI
Completeness conditions
- an operating accountability map
- working rituals, checklists, SOPs and Definition of Done
- knowledge-repository structure and direction for automation and AI
08 / ARTEFACTS AND DOCUMENTATIONBom Runtime™ / OPERATE
Every artefact retains a function in the wider architecture.
Accountability map
Roles, decision owners, RACI model, mandate scope and escalation routes.
Operating rhythm
Weekly, monthly and quarterly rituals governing priorities, reviews and updates.
Checklists and SOPs
Action sequence, performance conditions and accountability for repeatable processes.
Definition of Done
Criteria for completeness, quality, approval and material readiness for further use.
Knowledge repository
A structure of sources, statuses, versions, owners and access principles for the team and partners.
Direction for automation and AI
A map of workflows, integrations and tasks that can use the organisation's approved context.
09 / QUALITY GATESBom Runtime™ / OPERATE
Completeness is confirmed across seven distinct layers.
The assessment covers value, source material, decision, dependencies, documentation, learning rhythm and readiness. Each layer retains its own criterion.
Value
The material identifies the value activated, protected or structured by the system and the mechanism leading to that value.
Source material
Sources, context and information status make the basis of the work and the scope of accepted findings traceable.
Decision
Every resolution has an owner, status, rationale, consequences and a defined point for reassessment.
Dependencies
The effect of the decision on other layers, systems, roles and materials is recorded before transfer.
09.2 / QUALITY GATESBom Runtime™ / OPERATE
Readiness follows from documentation, rhythm and conditions for assuming responsibility.
The final part of the assessment proceeds from the governing version through the update mechanism to an outcome ready for further use.
Documentation
The governing version has a defined location, name, owner, date and relationship to dependent materials.
Rhythm and learning
Reviews, quality signals and usage data guide updates to decisions and source material.
Readiness
Conditions for completeness, acceptance and assumption of responsibility confirm that the outcome is ready for further use.
09.3 / FUNCTION → EFFECTBom Runtime™ / DESIGN
From each function to a concrete result.
Bom Runtime™ turns approved architecture into a repeatable operating practice with clear responsibility, sources, rhythm and quality.
Role
- Agency delivery
- Responsibility map covering work ownership, decision rights, interfaces and escalation.
- Concrete effect
- Each recurring responsibility and decision has an identifiable owner.
- Why it matters
- Explicit ownership shortens coordination and protects accountability.
- Bom Blueprint™ placement
- 04
- Further use
- Assign access, rhythm, workload and acceptance authority to the named role.
- Acceptance evidence
- Owner, backup, decision rights, inputs, outputs and escalation route are recorded.
Rhythm
- Agency delivery
- Operating rhythm for opening, executing, reviewing and closing daily, weekly and monthly work.
- Concrete effect
- Critical work and reviews occur at predictable moments with the required participants.
- Why it matters
- A repeatable rhythm converts standards and priorities into sustained practice.
- Bom Blueprint™ placement
- 04
- Further use
- Attach named records, checklists and decision gates to each recurring event.
- Acceptance evidence
- Cadence, agenda, owner, participants, inputs, outputs and overdue rule are recorded.
Source
- Agency delivery
- Source-of-Truth structure with authority, status, ownership, version and relationship rules.
- Concrete effect
- People and tools can find the current governing record for the task at hand.
- Why it matters
- Current sources protect decisions and delivery from version conflict and memory loss.
- Further use
- Connect each source to its process, owner, review date and dependent records.
- Acceptance evidence
- The register identifies the current version, authority, location, owner and review trigger.
09.4 / FUNCTION → EFFECTBom Runtime™ / DESIGN
Why the result matters and what it activates.
Each function ends with an accepted result, a stated business reason and a named route for further use.
Quality
- Agency delivery
- Definition of Done, checklists, quality signals and exception route for recurring work.
- Concrete effect
- People can determine whether work is complete, usable and ready for transfer.
- Why it matters
- Visible acceptance criteria stabilise quality across people, volume and time.
- Bom Blueprint™ placement
- 04
- Further use
- Use the criteria at review, acceptance, handover and Learning Loop events.
- Acceptance evidence
- Criteria, evidence type, reviewer, exception and corrective route are recorded.
Transfer
- Agency delivery
- Handover and onboarding record carrying scope, status, sources, ownership and readiness into the receiving role.
- Concrete effect
- Responsibility can change hands while context and acceptance conditions remain intact.
- Why it matters
- A controlled transfer protects continuity across clients, partners, specialists and internal roles.
- Further use
- Activate the receiving role's workflow, access and first review point.
- Acceptance evidence
- Both sides accept the material, status, owner, open conditions and next action.
AI context
- Agency delivery
- Structured context pack with approved sources, role boundaries, process logic and update rules for business AI use.
- Concrete effect
- AI-supported work receives current organisational context and a defined human decision owner.
- Why it matters
- Structured context and ownership improve reliability, traceability and responsible use.
- Bom Blueprint™ placement
- 06
- Further use
- Connect approved use cases to their source set, reviewer, quality gate and update rhythm.
- Acceptance evidence
- Use case, sources, permissions, owner, human review and update condition are recorded.
10 / ORGANISATIONAL OUTCOMESBom Runtime™ / OPERATE
Organisational capabilities after completing the system.
The outcome comprises the decision, ready-to-use material, maintenance conditions and the relationship with the next system accountability.
Decisions, standards and ways of working documented in the system.
Clear knowledge sources, priorities and quality criteria.
Readiness for scaling, integration and automation.
A repeatable working standard maintained through the organisation's rhythm.
11 / MAINTAIN AND OPERATE SUSTAIN THE SOURCE AND WAY OF OPERATINGBom Runtime™ / OPERATE
Maintain and Operate sustain the source and way of operating.
Maintain is responsible for the currency of decisions and materials. Operate governs their daily use. Separating these layers makes it possible to assess source quality, execution quality and the mechanism for returning knowledge to the system independently.
System and source register
A list of governing documents, decisions and tools with the owner of each entry.
Review rhythm
A review calendar covering an annual review and a review after a material change in the organisation or market.
Quality standard
Work-completion criteria, material-assessment method and conditions for a draft to become a source.
Governance
Naming principles, status register, decision route and method for resolving discrepancies.
AI context update
Maintenance of material used by tools together with a record of human accountability.
Learning loop
The return of usage findings to earlier decisions, allowing the completion of one cycle to open the next.
12 / SYSTEM TRANSFERBom Runtime™ / OPERATE
Relationships with the other systems.
The transfer identifies the material passed forward, its status, function and conditions for assuming responsibility.
Bom Blueprint™
source of decisions, model and operating architecture
→Bom Creation™
standard for asset production and maintenance
→Bom Flow™
handoff, onboarding and continued relationship
→Bom Perspective™
direction calibration following a change in environment or priorities
→13 / CONTEXT AND CONTINUITYBom Runtime™ / OPERATE
Context ready for work with AI.
Structured knowledge and processes make it possible to design workflows, prompts, integrations and automation around the real operating model, with visible decision ownership and quality criteria.
END / Bom Runtime™ / OPERATEBom Dia Creation™
The point of entry follows from the current context.
The conversation calibrates the scope, decision owner, success criteria and implementation readiness.
weare@bomdiacreation.com ↗