Frameworks and approved terms
Framework breakdowns
A practical map of the frameworks discussed and approved in the corpus, with working-term and future-facing items kept clearly labelled.
Diagram
Framework relationship map
Collective OS sits in the centre. Public service pillars sit above it. Internal leverage systems and governance patterns sit below it.
Framework register
What each framework is responsible for
Items labelled as approved can be treated as stable planning language. Working terms and future-facing items should be held more lightly until they are formally locked.
Collective OS
The internal operating system that connects delivery, workflows, dashboards, knowledge reuse, and agentic support.
- Source basis
- Accepted as the internal system name, while the public story stays outcome-led.
- Codex can deliver
- Maintain the OS map, workflow docs, standard page structures, SOPs, and source-indexed knowledge files.
- Human in the loop
- Approve which OS details can be exposed to clients, staff, contractors, and future partners.
Product pillars
Lead Generation, Demand Generation, Lead Development, and Advisory form the client-facing service architecture.
- Source basis
- Repeatedly approved as the replacement for Pitcher, Catcher, Closer as primary public language.
- Codex can deliver
- Draft service pages, intake forms, offer one-pagers, scope templates, and comparison tables.
- Human in the loop
- Set pricing, commercial boundaries, final naming, and client-specific promises.
Brand Implementation System
The practical brand, messaging, product, proof, tone, audience, and knowledge foundation required for execution.
- Source basis
- Favoured as the practical replacement for vague brand-system language, but not fully locked as final public naming.
- Codex can deliver
- Create questionnaires, extraction prompts, voice guides, message matrices, and reusable knowledge bases.
- Human in the loop
- Validate taste, strategic nuance, brand truth, client positioning, and the difference between useful foundation work and subjective brand drift.
Lead Intelligence Layer
A sidecar intelligence system for post-lead visibility, call analysis, qualification, objections, and feedback loops.
- Source basis
- Approved as the next major capability after Lead Generation standardisation and explicitly not a CRM replacement.
- Codex can deliver
- Design field schemas, call-summary formats, MQL/SQL logic drafts, dashboard views, and analysis workflows.
- Human in the loop
- Own privacy, consent, sales-context judgment, final qualification rules, and client relationship decisions.
Atomic Flywheel
Extract domain knowledge once, then reuse it across blogs, social, ads, pages, thought leadership, and sales assets.
- Source basis
- Accepted as an internal knowledge and content amplification capability.
- Codex can deliver
- Atomise approved source material into channel-specific drafts, content calendars, briefs, and repurposing workflows.
- Human in the loop
- Approve public claims, expertise, voice, case-study proof, and what should not be published.
Human-to-agentic workflow governance
Map, standardise, benchmark, augment, compare, version, promote, and retain rollback for each workflow.
- Source basis
- The raw transcript treats this as one of the strongest parts of the model.
- Codex can deliver
- Build benchmark rubrics, run QA comparisons, maintain workflow docs, and create validation checklists.
- Human in the loop
- Decide quality thresholds, handle exceptions, accept risk, and keep a human owner for every workflow.
Execution modules
Sellable and assignable delivery units such as Lead Page Sprint, Campaign Launch Sprint, brochure sprint, and dashboard setup.
- Source basis
- Approved as a way to productise live work while feeding the broader OS.
- Codex can deliver
- Package modules into briefs, checklists, handoff docs, task plans, QA guides, and delivery templates.
- Human in the loop
- Approve scope, timelines, commercial fit, client priority, and when a module becomes a standalone offer.
Dashboard tiers
Marketing Performance, Lead Intelligence, Revenue Intelligence, and Executive Growth dashboards map to client maturity.
- Source basis
- Strong planning element in the CKF, with formula definitions still incomplete.
- Codex can deliver
- Draft metric dictionaries, dashboard wireframes, data schemas, and reporting narratives.
- Human in the loop
- Confirm data accuracy, metric definitions, attribution assumptions, and strategic interpretation.
Stratosphere Group
The property-specific acquisition arm powered by Collective for developers and project-based property sales.
- Source basis
- Retained because property needs a simpler, category-specific front door.
- Codex can deliver
- Draft property-specific pages, lead page templates, campaign briefs, and Stratosphere positioning updates.
- Human in the loop
- Own property-market credibility, proof, sales relationships, client approvals, and final positioning.
HyperCTRL.ai
Potential future IP, technology, or OS entity that may power Collective, Stratosphere, and other delivery arms.
- Source basis
- Correct spelling is approved, but the current instruction is to keep it internal/future-facing.
- Codex can deliver
- Preserve naming consistency and document future architecture options without making it a current build priority.
- Human in the loop
- Decide if and when HyperCTRL.ai becomes a real product, legal entity, brand, or technology surface.