Artifact Library.
The work is only useful if something ships.
Strategy decks gather dust. Artifacts get used. Every engagement here resolves into something concrete — an ICP map, a RACI, an output policy, an incrementality model — that a named role picks up and uses to make one specific decision. This is the catalogue of artifact types the work produces, mapped to the decision each one unblocks.
Filter 55 artifact types by category:
No artifacts match that filter.
Go-to-market
Where the market is, who buys, and the sequence to win it.
-
Market Entry Audit
Unblocks Where the US motion starts, what to ignore, and whether to enter now or fix first.
Details: Market Entry Audit
A structured read of US-market readiness across product-market fit, GTM, sizing, BD, monetization, talent, and privacy posture. The 7-step diagnostic that opens most engagements.
- Used by
- What's inside
-
- PMF + ICP read
- Market sizing + wedge
- BD framework
- Monetization model
- Talent + privacy posture
- 90-day execution plan
- Related
-
ICP Map
Unblocks Which buyer segment deserves immediate focus, and in what order the rest follow.
Details: ICP Map
A sequenced map of who to sell to — tiered by readiness and proof-travel speed — so the motion compounds instead of spraying every segment in parallel.
- Used by
- What's inside
-
- Primary / secondary / strategic tiers
- Fit criteria per tier
- Trigger moments
- Disqualifiers
- Sequencing rationale
- Related
-
Buyer Narrative
Unblocks How to position the product so it lands with brand / agency / enterprise committees.
Details: Buyer Narrative
The translation of technical wins into the language a buying committee actually evaluates — reframing the category so the product reads as a budget line, not an experiment.
- Used by
- What's inside
-
- Category reframe (from / to)
- Core promise
- Proof points
- Committee-by-committee translation
- Objection pre-empts
- Related
-
Named Account Sequence
Unblocks Which accounts to pursue first and how to enter each one.
Details: Named Account Sequence
A target-account list with decision-maker mapping, entry points, and an outreach sequence — the first-pipeline workplan, not a CRM dump.
- Used by
- What's inside
-
- Target accounts + tiers
- Decision-maker map per account
- Entry point / warm path
- Sequence + cadence
- Pipeline dashboard hooks
- Related
-
Competitor Takeover Matrix
Unblocks Where to attack a competitor and where to deliberately not engage.
Details: Competitor Takeover Matrix
A peer-set read that names where not to compete, where to win, and the wedge against each category of competitor — built for displacement, not feature parity.
- Used by
- What's inside
-
- Peer-set grouping
- Do-not-compete-on list
- Win-on dimensions
- Displacement plays
- Proof requirements per play
- Related
-
First 25 Target Accounts
Unblocks Which lighthouse wins to chase so early proof compounds across the segment.
Details: First 25 Target Accounts
A focused lighthouse-account list — the smallest set of accounts whose wins travel furthest as proof — with a rationale for why each one matters.
- Used by
- What's inside
-
- 25 named accounts
- Lighthouse rationale
- Proof-travel value
- Entry hypothesis
- Owner per account
- Related
Operating model
How the commercial system runs — roles, rights, capacity, cadence.
-
RACI
Unblocks Who owns each recurring decision once founder-led sales hits its ceiling.
Details: RACI
Responsible / Accountable / Consulted / Informed assignments across the commercial decisions that keep stalling — so ownership is explicit, not assumed.
- Used by
- What's inside
-
- Decision rows
- Responsible
- Accountable
- Consulted
- Informed
- Related
-
Decision Rights Matrix
Unblocks Which decisions a role can make alone, and which require escalation.
Details: Decision Rights Matrix
A map of which role makes — versus advises on — each class of commercial decision, with escalation thresholds. The antidote to decisions stuck in committee.
- Used by
- What's inside
-
- Decision class
- Decider vs advisor
- Escalation threshold
- Approval cadence
- Audit trail
- Related
-
Capacity Model
Unblocks How many reps to hire, when, and against what productivity assumptions.
Details: Capacity Model
Rep productivity and territory math that ties headcount to pipeline and ACV trajectory — operator math for hiring decisions, not pitch math.
- Used by
- What's inside
-
- Productivity per FTE
- ACV trajectory
- Territory coverage
- Ramp assumptions
- Pipeline-to-quota math
- Related
-
Role Scorecard
Unblocks What the next commercial hire is accountable for and how to evaluate candidates.
Details: Role Scorecard
A hiring scorecard defining the outcome a role must deliver, the competencies behind it, and the first-90-day measures — so the next hire is designed, not improvised.
- Used by
- What's inside
-
- Mission / outcome
- Key competencies
- First-90-day measures
- Comp framing
- Sourcing profile
- Related
Show all 10 Show fewer
-
0-3-6-12 Cadence
Unblocks What ships in each phase and what gate must clear before the next.
Details: 0-3-6-12 Cadence
A phased operating plan — readiness, first pipeline, repeatable motion, scale without bloat — with a milestone gate at each stage. The cadence a retainer runs on.
- Used by
- What's inside
-
- Phase intents
- Per-phase deliverables
- Milestone gates
- Weekly decision cadence
- Owner per phase
- Related
-
Revenue Operating System
Unblocks How sales, marketing, and customer success operate as one accountable system.
Details: Revenue Operating System
The integrated system that turns founder-led selling into a repeatable motion — sales, marketing, and post-sale operating as one quota-linked function with shared definitions.
- Used by
- What's inside
-
- M-Sales / D-Sales construct
- Pipeline-stage definitions
- Forecast discipline
- CRM + BI standardization
- Expansion / renewal motion
- Related
-
Agentic use-case map
Unblocks Which agentic workflows to build first, and which pilots to stop.
Details: Agentic use-case map
A prioritized map of candidate agentic use cases scored by value, feasibility, data readiness, and governance risk — so investment goes to workflows that can actually move from pilot to production.
- Used by
- What's inside
-
- Candidate workflows
- Value + feasibility score
- Data + tool readiness
- Governance risk
- Pilot-to-production priority
- Related
-
Decision rights matrix
Unblocks What an agent is allowed to decide alone, and where a human must approve.
Details: Decision rights matrix
A map of which decisions an agent may make autonomously, which require a human in the loop, and which are out of scope — with escalation and approval thresholds for each.
- Used by
- What's inside
-
- Decision class
- Autonomous vs human-in-the-loop
- Escalation threshold
- Approver / owner
- Out-of-scope list
- Related
-
Governance and fallback model
Unblocks How an agent is governed in production, and what it does when it cannot proceed safely.
Details: Governance and fallback model
The guardrails for a live agent — output policy, permission limits, monitoring, and the fallback logic that defines what happens when the agent is uncertain, fails, or hits a boundary.
- Used by
- What's inside
-
- Output policy
- Permission + rate limits
- Monitoring + alerts
- Fallback / human-handoff logic
- Incident + rollback path
- Related
-
30/60/90 agentic deployment path
Unblocks What ships in each phase of an agentic deployment and what gate clears before the next.
Details: 30/60/90 agentic deployment path
A phased plan for moving an agentic workflow from pilot to governed production — readiness, supervised rollout, and scaled deployment — with a gate that must clear before each phase.
- Used by
- What's inside
-
- Phase 1 readiness
- Phase 2 supervised rollout
- Phase 3 scaled deployment
- Per-phase gates
- Owner + success metric
- Related
Data & platform
How governed data becomes a packaged, shippable product or workflow.
-
Data and tool access map
Unblocks Which data and tools an agent can touch, with what permissions.
Details: Data and tool access map
The allow-listed set of data sources and tools an agent may read, write, or call — with permissions, scopes, and audit hooks. Defines the agent's operational boundary.
- Used by
- What's inside
-
- Approved data sources
- Approved tools / APIs
- Read / write / call scopes
- Permission boundaries
- Audit + lineage hooks
- Related
-
Agentic workflow blueprint
Unblocks How a specific agentic workflow is structured, owned, and judged end to end.
Details: Agentic workflow blueprint
An end-to-end design of a single agentic workflow across its layers — signals, context, tools, decisions, governance, and outcomes — with the owner and success metric for each step.
- Used by
- What's inside
-
- Signal + context inputs
- Tool + data calls
- Decision + control points
- Governance + fallback
- Outcome metric + owner
- Related
-
Platform-Fit Matrix
Unblocks Which platform owns which decision, and where the workflow should live.
Details: Platform-Fit Matrix
A vendor-neutral read of which environment fits which collaboration workflow — clean rooms, secure sharing, warehouse-native, walled gardens — by use case, not by logo.
- Used by
- What's inside
-
- Fit / misfit conditions
- Capability map
- Output rules
- Governance load
- POC-to-production path
- Related
-
Output Policy
Unblocks What can leave the environment — aggregate, score, audience, or export.
Details: Output Policy
The rules for what can leave a collaboration environment — aggregate thresholds, allowed exports, re-review triggers. The real control surface in sensitive data work.
- Used by
- What's inside
-
- Allowed outputs
- Aggregate thresholds
- Export rules
- Re-review triggers
- Audit + approval workflow
- Related
Show all 11 Show fewer
-
Collaboration Canvas
Unblocks Whether the data and governance are ready for collaboration before tool selection.
Details: Collaboration Canvas
A pre-platform map of the data footprint, governance model, sensitivity, consent, and access policy — settled before any platform is selected.
- Used by
- What's inside
-
- Data footprint
- Ownership map
- Sensitivity + consent basis
- Access policy
- Counterparty posture
- Related
-
Clean Room Operating Model
Unblocks How to run clean-room collaboration as a repeatable operating model, not a one-off.
Details: Clean Room Operating Model
How a clean room actually runs as a workflow — templates, permitted joins, output policy, and the operating cadence that turns a one-off match study into infrastructure.
- Used by
- What's inside
-
- Templates + permitted joins
- Output policy
- Role + governance design
- Refresh cadence
- Production path
- Related
-
Semantic Infrastructure Map
Unblocks Which definitions and mappings must exist before business-user or agent analytics is trustworthy.
Details: Semantic Infrastructure Map
The map of metric definitions, taxonomies, IDs, and mappings that lets humans, platforms, and agents interpret data consistently — the layer usually missing until fragmentation hurts.
- Used by
- What's inside
-
- Metric definitions
- Taxonomies + value dictionaries
- ID + key relationships
- Synonyms / business language
- Benchmarks + feedback loop
- Related
-
POC-to-Production Plan
Unblocks What turns a working POC into a renewed, multi-year production workflow.
Details: POC-to-Production Plan
The checklist that turns a proof-of-concept into governed, repeatable infrastructure — use case, owner, success metric, output rules, and the path after the POC works.
- Used by
- What's inside
-
- Single-decision use case
- Data footprint + owner
- Output rules
- Success metric
- Production + renewal path
- Related
-
Standards Layer Map
Unblocks Which standards layers a product or agentic workflow actually touches, and which official specs to validate first.
Details: Standards Layer Map
A one-page map of the standards stack agentic advertising depends on — workflow protocols, runtime and signal exchange, transaction rails, privacy constraints, measurement trust, and research evidence — so a roadmap names the layers it touches instead of treating "standards" as one thing.
- Used by
- What's inside
-
- Layer (workflow → evidence)
- Standards in the layer
- Owning body
- Status to validate
- Integration exposure
- Related
-
Core AdTech Rails Map
Unblocks Which rails an integration must speak, at which versions, before agentic workflows can transact over them.
Details: Core AdTech Rails Map
The transaction-rail inventory under a media or data product — OpenRTB, AdCOM, OpenDirect, Deals API, VAST, ads.txt / app-ads.txt, sellers.json, the SupplyChain Object, and the taxonomies — with the version in play and the official source to validate against.
- Used by
- What's inside
-
- Rail / spec
- Version in play
- Where it sits in the transaction flow
- Supply-chain transparency posture
- Official source to validate
- Related
-
Privacy Constraint Map
Unblocks Which consent, deletion, and platform constraints bind a data flow before it ships.
Details: Privacy Constraint Map
A map of the consent and privacy signals a data flow must carry and honor — GPP / TCF strings, deletion-request propagation, and platform / OS attribution constraints — built so privacy posture is designed in, not retrofitted after legal review.
- Used by
- What's inside
-
- Jurisdiction / surface
- Signal carried (GPP, TCF)
- Deletion propagation path
- Platform / OS constraint
- Status to validate
- Related
Measurement
How value is proven — incrementality, MMM inputs, and proof taxonomy.
-
Evaluation model
Unblocks Whether an agent is good enough to deploy, and how its quality is tracked over time.
Details: Evaluation model
The test design for whether an agent produces correct, useful, and safe outputs — task-level checks, outcome-level metrics, and the cadence for re-evaluation as inputs drift.
- Used by
- What's inside
-
- Task-level test set
- Outcome-level metrics
- Pass / fail thresholds
- Drift + re-evaluation cadence
- Human-review sampling
- Related
-
Incrementality Model
Unblocks Whether spend is causing incremental outcomes or harvesting demand that would convert anyway.
Details: Incrementality Model
A test design that separates real, caused value from harvested demand — the causal source of truth that keeps optimization honest. Attribution is not incrementality.
- Used by
- What's inside
-
- Test / holdout design
- Geo-lift structure
- Source of truth
- Read-out method
- Decision thresholds
- Related
-
MMM Input Map
Unblocks Whether the inputs are clean and complete enough to trust an MMM read.
Details: MMM Input Map
The disciplined inputs a marketing-mix model needs — channel, spend, KPI, geo, time, priors, and business context — mapped before the model is run, not after.
- Used by
- What's inside
-
- Channel + spend taxonomy
- KPI definitions
- Geo + time granularity
- Priors + business context
- Reconciliation rules
- Related
-
Proof Taxonomy
Unblocks Which proof a given buyer accepts, and how to keep metrics comparable across sources.
Details: Proof Taxonomy
A classification of what counts as proof for each buyer — what each network or platform metric does and does not mean — so claims travel without losing comparability.
- Used by
- What's inside
-
- Proof types by buyer
- Metric definitions
- Comparability rules
- What each metric excludes
- Source-of-truth mapping
- Related
Show all 13 Show fewer
-
BI / Reporting Model
Unblocks Which metrics are governed, owned, and comparable enough to run the business on.
Details: BI / Reporting Model
Governed metrics and a reporting model with defined ownership — moving past dashboards that report toward a model that drives decisions and feeds the feedback loop.
- Used by
- What's inside
-
- Governed metric definitions
- Metric ownership
- Reporting cadence
- Feedback loop hooks
- Decision triggers
- Related
-
Readiness Scorecard
Unblocks Where you fit, how ready you are, and which engagement path to start with.
Details: Readiness Scorecard
A self-serve diagnostic that scores readiness across the six engagement paths and routes to the right next step — the no-email, browser-stored entry point to the work.
- Used by
- What's inside
-
- Six-path scoring
- Per-path readiness signals
- Recommended next step
- Surface / agent-readiness read
- Browser-stored result
- Related
-
Evidence Hierarchy Map
Unblocks Which evidence is strong enough to move budget, workflow, or product strategy.
Details: Evidence Hierarchy Map
A one-page ordering of evidence strength — exposure, attention, persuasion, behavior, incrementality, business value, comparability — so an agent or analyst knows which level a metric actually proves before it informs a decision.
- Used by
- What's inside
-
- Evidence levels
- What each level proves
- What it does not prove
- Method per level
- Collapse risks
- Related
-
Measurement Science Stack
Unblocks Which level of evidence a given metric represents before it is used to decide.
Details: Measurement Science Stack
The exposure-to-comparability stack made explicit, with the question answered and the watch-out at each level — the artifact that stops agentic optimization from collapsing seven levels of evidence into one easy metric.
- Used by
- What's inside
-
- Level
- Question answered
- Risk / watch-out
- Method
- Decision use
- Related
-
Research Validation Checklist
Unblocks Whether a research or measurement claim is valid enough to act on or cite.
Details: Research Validation Checklist
A pre-citation checklist for research and measurement claims — source and recency, method and sample, proxy quality, bias checks, stated limitations, and reproducibility — before a number is used to decide or quoted externally.
- Used by
- What's inside
-
- Source + recency
- Method + sample
- Proxy quality
- Bias checks
- Stated limitations
- Reproducibility
- Related
-
Agentic Measurement Guardrail
Unblocks When an agent may recommend, when a human must approve, and when an action is blocked.
Details: Agentic Measurement Guardrail
The decision-threshold spec for an agentic system: which evidence lets an agent recommend, which requires human approval, and which blocks action — so budget never moves on a weak proxy at machine speed.
- Used by
- What's inside
-
- Metric + evidence level
- Recommend / approve / block thresholds
- Required causal check
- Audit trail
- Escalation path
- Related
-
Causal Proof Matrix
Unblocks Which measurement method to trust for a given budget or causal question.
Details: Causal Proof Matrix
A side-by-side of measurement methods — attribution, incrementality tests, MMM, brand lift, attention, and BI / finance reconciliation — with what each is best for and where each misleads, so agents do not optimize correlation at machine speed.
- Used by
- What's inside
-
- Method
- Best for
- Watch-out
- Causal strength
- Cost / latency
- Related
-
Cross-Platform Measurement Map
Unblocks Whether outcomes can be compared across platforms before a cross-platform plan is set.
Details: Cross-Platform Measurement Map
A map of how exposure, identity, deduplication, outcome, and currency are defined across linear, streaming, CTV, digital, and retail media — so a cross-platform plan compares like with like instead of stacking incompatible definitions.
- Used by
- What's inside
-
- Platform / channel
- Exposure definition
- Identity + dedup
- Outcome definition
- Currency / comparability
- Related
-
Media Quality Guardrail Map
Unblocks Which media-quality thresholds and verification signals gate spend — and what an agent may optimize against.
Details: Media Quality Guardrail Map
The verification guardrails on a media workflow — MRC viewability definitions, GIVT / SIVT filtration, OM SDK measurement coverage, and certification expectations — made explicit before spend or agent optimization runs against them.
- Used by
- What's inside
-
- Surface / channel
- Viewability definition
- IVT filtration (GIVT / SIVT)
- Measurement coverage (OM SDK)
- Certification expectations
- Related
Commercial proof
What travels into the deal room — narrative, objections, board reads.
-
Case-Study Template
Unblocks How to package a win so it travels as proof across the segment.
Details: Case-Study Template
A repeatable structure for building proof that travels — problem, approach, what shipped, and what the buyer can replicate — designed so each win compounds the next pitch.
- Used by
- What's inside
-
- Problem framing
- Approach + what shipped
- Buyer-replicable takeaway
- Verticalization hooks
- Quote / sign-off structure
- Related
-
Objection Pack
Unblocks How to answer the objection that is currently stalling the deal.
Details: Objection Pack
The recurring stalls a buying committee raises — brand safety, comparability, measurement — paired with the reframe and the proof that answers each one.
- Used by
- What's inside
-
- Objection list
- Reframe per objection
- Proof / evidence
- Who raises it
- Escalation handling
- Related
-
Board-Ready One-Pager
Unblocks The board-grade decision in front of the company — entry, expansion, or reset.
Details: Board-Ready One-Pager
A single page that frames a board-grade decision — the market read, the options, the recommendation, and the risk — written for a board, not a sales deck.
- Used by
- What's inside
-
- Market read
- Options + trade-offs
- Recommendation
- Risk + mitigations
- Decision ask
- Related
-
Sales Narrative
Unblocks The single story the commercial team tells, consistently, in every room.
Details: Sales Narrative
The story the whole commercial team tells the same way — the category frame, the stakes, and the path — so positioning does not drift rep by rep.
- Used by
- What's inside
-
- Category frame
- Stakes / why now
- Promise + proof
- Discovery questions
- Talk track + escalation
- Related
Show all 15 Show fewer
-
QBR / JBP Structure
Unblocks How to run the QBR / JBP so it drives expansion, not just renewal.
Details: QBR / JBP Structure
A structure for quarterly business reviews and joint business plans that turns a renewal conversation into an expansion one — value delivered, value ahead, shared plan.
- Used by
- What's inside
-
- Value-delivered review
- Value-ahead roadmap
- Shared goals + owners
- Expansion hypotheses
- Next-quarter plan
- Related
-
MSales Feedback Loop
Unblocks How marketing, sales, and customer signal feed one shared revenue loop instead of separate functions.
Details: MSales Feedback Loop
Maps how marketing signal, sales conversations, buyer objections, proof assets, pipeline movement, and customer feedback inform one revenue system.
- Used by
- What's inside
-
- Market signal inputs
- Sales conversation feedback
- Buyer objection log
- Proof-asset map
- Pipeline + customer-feedback loop
- Related
-
Revenue Supply Chain
Unblocks How much pipeline, at what conversion and ACV, the revenue target actually requires.
Details: Revenue Supply Chain
Works backward from ARR target to pipeline, ACV, conversion rates, MQL / SQL volume, and operating cadence.
- Used by
- What's inside
-
- ARR target decomposition
- Pipeline coverage model
- ACV + conversion rates
- MQL / SQL volume map
- Operating cadence
- Related
-
Buyer Signal Map
Unblocks Which buyer signals to act on, and what the next-best action is for each.
Details: Buyer Signal Map
Connects intent, content engagement, sales notes, objections, customer feedback, and product usage to next-best actions.
- Used by
- What's inside
-
- Intent + content engagement
- Sales notes + objections
- Customer feedback
- Product-usage signals
- Next-best-action routing
- Related
-
Offer architecture canvas
Unblocks What the productized offer actually is — problem, scope, delivery, and boundaries.
Details: Offer architecture canvas
A map of the buyer problem, the offer that solves it, what is in and out of scope, and how the offer is delivered — the structure that turns a capability into a defined, sellable product.
- Used by
- What's inside
-
- Buyer problem
- Offer + in/out of scope
- Delivery model
- Required capabilities
- Expansion path
- Related
-
Packaging and tiering model
Unblocks How to package the offer into tiers so buyers can self-select and expand.
Details: Packaging and tiering model
How the offer is split into tiers or modules a buyer can choose between — what each tier includes, who it is for, and the upgrade path between them.
- Used by
- What's inside
-
- Tier / module definitions
- Inclusions per tier
- Target buyer per tier
- Upgrade triggers
- Edition boundaries
- Related
-
Pricing and value metric map
Unblocks What to charge for, on which value metric, and how price scales with value.
Details: Pricing and value metric map
The pricing model tied to the value metric the buyer actually grows on — what is charged for, how it scales, and why the metric aligns price with the value delivered.
- Used by
- What's inside
-
- Value metric
- Pricing model
- Price scaling logic
- Discount / floor rules
- Competitive price frame
- Related
-
POC-to-production blueprint
Unblocks What converts a POC into a paid, repeatable production deal.
Details: POC-to-production blueprint
The path that turns a successful proof-of-concept into a renewed, productized engagement — success criteria, commercial owner, conversion terms, and the steps from pilot to production revenue.
- Used by
- What's inside
-
- POC success criteria
- Conversion terms
- Commercial owner
- Production scope
- Renewal / expansion path
- Related
-
Proof taxonomy
Unblocks Which proof each buyer role requires, and where each piece comes from.
Details: Proof taxonomy
A classification of the proof each buyer in the committee needs — pilots, references, benchmarks, security, ROI — mapped to where it comes from, so the deal is not stalled on a missing receipt.
- Used by
- What's inside
-
- Proof types by buyer role
- Source per proof
- Strength / status
- Gaps to close
- Deal-stage mapping
- Related
-
Buyer committee narrative
Unblocks How to frame the offer for each role on the buying committee.
Details: Buyer committee narrative
The story tuned for each member of an enterprise buying committee — economic buyer, technical buyer, user, and blocker — so a single deal lands with every role that has to say yes.
- Used by
- What's inside
-
- Committee roles
- Per-role value frame
- Per-role objection + answer
- Required proof per role
- Champion enablement
- Related
-
Bespoke vs productized decision model
Unblocks Which capabilities to productize and which to keep as custom delivery.
Details: Bespoke vs productized decision model
A framework for deciding which work to keep bespoke and which to productize — based on repeatability, margin, demand pattern, and delivery cost — so productization effort goes where it pays back.
- Used by
- What's inside
-
- Repeatability score
- Margin + delivery cost
- Demand pattern
- Productize / keep-bespoke call
- Sequencing rationale
- Related
Signal containerization artifacts
The companion set to the signal-containerization essay — the artifacts that turn a raw signal into an executable, governed object an agent can discover, activate, and evaluate. Each is described as a structure, not a template, and links back to the essay that frames it.
-
Signal Container Canvas
Unblocks Whether a signal is defined completely enough to be activated and audited as a single object.
Details: Signal Container Canvas
Maps intent, semantics, provenance, policy, activation, and evaluation for an executable signal object.
- Used by
- What's inside
-
- Intent + meaning
- Semantics + identifiers
- Provenance + lineage
- Policy + allowed use
- Activation routes
- Evaluation hooks
- Related
-
Dual-Path Activation Map
Unblocks Which activation route a signal takes, and what happens when identity or context is unavailable.
Details: Dual-Path Activation Map
Shows how a signal can activate through identity and contextual routes, including fallbacks and governance.
- Used by
- What's inside
-
- Identity route
- Contextual route
- Route-selection logic
- Fallback handling
- Governance + consent checks
- Related
-
Agentic Signal Workflow
Unblocks How an agent moves a signal from discovery to evaluated outcome, end to end.
Details: Agentic Signal Workflow
Defines how an agent discovers, checks, activates, monitors, and evaluates signal containers.
- Used by
- What's inside
-
- Discovery + selection
- Policy + readiness checks
- Activation step
- Monitoring + alerts
- Evaluation + feedback
- Related
-
Signal Governance Checklist
Unblocks Whether a signal meets the governance bar required to activate and to leave the environment.
Details: Signal Governance Checklist
Documents source, method, freshness, privacy, expansion, allowed outputs, and audit rules.
- Used by
- What's inside
-
- Source + method
- Freshness + decay
- Privacy + consent basis
- Expansion limits
- Allowed outputs
- Audit + review rules
- Related
How artifacts map to services
Artifacts are not a menu you order from. They are the natural output of an engagement — the diagnostic produces a read, an audit produces a plan, a sprint produces pipeline, a retainer produces the operating system. Each shape tends to ship the categories below.
- 01
Self-serve diagnostic — scores the six paths and routes to the right next step.
- A readiness read
- A recommended path
- 02
2–3 week diagnostic across seven lenses into a 90-day plan.
- 03
6–8 week execution sprint — pipeline, partner co-sell, pricing tests.
- 04
3, 6, or 12 months of senior operator partnership on a weekly cadence.
If you can name the decision that is stalling, you can name the artifact that unblocks it. Scope the set that fits your problem — or start with the scorecard if you're not sure which one.