How thercha/bone-and-bloom-agency-os works
Purpose and Entry Points
This repository is the canonical, versioned operating system for Bone & Bloom advertising commercialisation—not an application runtime. It defines how a completed product moves through a repeatable campaign lifecycle. Start operational work with AGENCY_DNA_PACK.md, the assigned manual in roles/, the authority mapping in DECISION_MATRIX.md, then the task SOP in sops/ and its referenced template in templates/.
Governance and Change Control
The operating model is constrained by product requirements, constitutional rules, standards, and architecture decisions. PRODUCT_REQUIREMENTS_DOCUMENT.md, OPERATING_MODEL.md, and SYSTEM_BLUEPRINT.md define the top-level system; PROJECT_CHARTER.md governs contributions. Structural changes require ADRs under adr/, while release sequencing and implementation work flow through BUILD_QUEUE.md and RELEASE.md. The Founder owns constitutional/major direction; the Lead Systems Architect owns structure and release sequencing; the Lead Engineer maintains repository integrity.
Authority and Capability Model
Work is assigned through role ownership and decision rights rather than ad hoc collaboration. ORGANISATION_CHART.md, DECISION_MATRIX.md, and role manuals such as roles/ROLE-Operations-Manager.md establish responsibility and approval boundaries. Capability manuals in capabilities/ define the agency’s functional domains—strategy, research, creative, copy, analytics, media buying, operations, brand, and organisational memory—independent of specific tools or platforms.
Campaign Execution Pipeline
A campaign instance is initialized from execution/CAMPAIGN-SKELETON/, with stage-specific artifacts separated into intake, research, strategy, creative, copy, media, reviews, reports, and tests. The primary control flow is encoded by sops/SOP-01-Product-Intake.md through launch in sops/SOP-09-Meta-Campaign.md: intake → product understanding → audience research → strategy → creative/copy/production → quality review → campaign launch. Each handoff is intended to have an owner, template, and approver.
Measurement, Learning, and Reuse
After launch, performance operations form the feedback loop: reporting, optimisation, scaling, creative testing, retrospective learning, organisational memory, and archive. Key process contracts are sops/SOP-13-Reporting.md, sops/SOP-14-Optimisation.md, sops/SOP-16-Scaling.md, sops/SOP-17-Creative-Testing.md, sops/SOP-10-Organisational-Memory.md, and sops/SOP-18-Archive.md. Validated findings are persisted under memory/—including memory/insights/, memory/audience-insights/, memory/creative-patterns/, and memory/benchmarks/—so subsequent campaigns inherit evidence rather than recreate it.
Artifact Contracts, Runtime, and External Boundary
Templates are the output contracts joining SOP stages, roles, and campaign directories; examples include templates/TEMPLATE-Strategy-Brief.md, templates/TEMPLATE-Creative-Brief.md, templates/TEMPLATE-Media-Plan.md, and templates/TEMPLATE-Performance-Report.md. The material runtime is a documentation repository under version control, with GitHub Issues/Projects/PRs explicitly part of Lead Engineer execution. Meta is the named campaign-launch platform via sops/SOP-09-Meta-Campaign.md; no executable service, database, or application infrastructure is represented. Client-specific work is bounded under clients/bone-and-bloom/, while the OS excludes product creation, manufacturing, finance, HR, legal, and customer support.
Main entry points: SOP-13-Reporting.md Performance Operations · SOP-01-Product-Intake.md Intake & Research · BUILD_QUEUE.md Build & Release Control · TEMPLATE-Strategy-Brief.md Strategy
Components 21
Governance
System authority and controlled change.
- System Definition · Defines the commercialisation OS and its constraints.
OPERATING_MODEL.md - Product Requirements
PRODUCT_REQUIREMENTS_DOCUMENT.md - System Blueprint
SYSTEM_BLUEPRINT.md - Contribution Governance · Controls repository contributions and major change.
PROJECT_CHARTER.md - Architecture Decisions · Required for structural changes.
- Build & Release Control · Sequences implementation and releases.
BUILD_QUEUE.md
Operating Contracts
Reusable responsibilities and process contracts.
- Agency DNA Pack · Starting context for operational work.
AGENCY_DNA_PACK.md - Authority Model · Maps ownership and approval boundaries.
DECISION_MATRIX.md - Role Manuals · Assign execution ownership by role.
- Capability Manuals · Defines cross-tool agency capabilities.
- SOP Library · Defines stage handoffs, owners, approvals, and procedures.
- Template Library · Standard outputs consumed by campaign stages.
Campaign Lifecycle
Client work progresses through controlled stages.
- Campaign Skeleton · Initializes stage-separated campaign artifacts.
- Intake & Research · Captures product context and audience evidence.
sops/SOP-01-Product-Intake.md - Strategy · Converts research into campaign direction.
templates/TEMPLATE-Strategy-Brief.md - Creative, Copy & Production · Produces campaign assets from approved briefs.
templates/TEMPLATE-Creative-Brief.md - Review & Meta Launch · Quality-gates and launches the campaign on Meta.
sops/SOP-09-Meta-Campaign.md - Bone & Bloom Client Space · Bounds client-specific work within the OS.
Learning Loop
Performance evidence is retained for reuse.
- Performance Operations · Reports, optimises, scales, and tests live campaigns.
sops/SOP-13-Reporting.md - Organisational Memory · Persists reusable campaign findings.
- Campaign Archive · Closes and preserves completed campaign records.
sops/SOP-18-Archive.md
Connections 20
- Product Requirements → System Definition: constrains
- System Blueprint → System Definition: architects
- Contribution Governance → Architecture Decisions: requires
- Architecture Decisions → Build & Release Control: feeds approved changes to
- Agency DNA Pack → Role Manuals: orients work in
- Authority Model → Role Manuals: assigns decision rights to
- Capability Manuals → SOP Library: inform
- Role Manuals → SOP Library: own execution of
- SOP Library → Template Library: specify outputs with
- Template Library → Campaign Skeleton: populate
- Bone & Bloom Client Space → Campaign Skeleton: contains instances of
- Campaign Skeleton → Intake & Research: starts
- Intake & Research → Strategy: evidence informs
- Strategy → Creative, Copy & Production: briefs
- Creative, Copy & Production → Review & Meta Launch: submits for review and
- Review & Meta Launch → Performance Operations: live campaign measured by
- Performance Operations → Organisational Memory: validates and stores findings in
- Organisational Memory → Intake & Research: evidence reused by
- Performance Operations → Campaign Archive: closes into
- Build & Release Control → SOP Library: sequences repository delivery of