OTAH GTM Coordinator

Settings

Authorization boundary: this workspace drafts, records and evaluates only. It cannot send, publish, schedule, spend or export customer data. Hover a locked action for the authorization it requires.

Settings

Versions, evidence conventions, readiness definitions and the authorization boundaries this workspace runs under. Read-only by design.

Versions

App
v0.1.0
SDK
0.1.0
Context pack
v1.0
Brief generator
template-fill/0.1.0
Evaluation threshold
85%

Data handling

  • Sample data only: SOURCE-REPORTED capsule content, PROPOSAL readiness and SYNTHETIC economics.
  • No live integrations, connectors or customer records.
  • Every query is brand-scoped; records never mix across brands.
  • Retrieved text is treated as data, never as instructions.
  • No recurring work or schedules are created by this workspace.

Completeness weights

A PROPOSED heuristic: each of 10 activation fields scores by its evidence status, out of 2.

  • SOURCE1
  • HYPOTHESIS0.5
  • APPROVED1.5
  • VERIFIED2
  • PROPOSAL0.5
  • SYNTHETIC0
  • UNKNOWN0

Evidence classes

SOURCE-REPORTED

Read from a document/Notion page; not independently tested.

HYPOTHESIS

Proposed by analysis; not validated.

APPROVED

Owner-approved for a named use.

VERIFIED

Independently confirmed in production.

PROPOSAL

Suggested; not accepted.

SYNTHETIC

Invented for testing/illustration only.

UNKNOWN

No usable evidence. Never filled with a guess, zero or midpoint.

Readiness levels (proposed, not assigned)

  1. Unknown

    No accepted evidence about buyer, offer or delivery.

  2. Discovery

    Buyer/job/offer hypotheses exist; learning, not selling at scale.

  3. Pilot-ready

    Offer, scope, capacity and authorization defined for a bounded pilot.

  4. Pilot-observed

    A pilot ran and outcomes were recorded against a denominator.

  5. Repeatable

    Outcomes reproduced across more than one cohort with stable delivery.

  6. Scale-ready

    Economics, capacity and controls support expansion.

Knowledge layers (context maintenance v1.0)

  1. Project instructions: durable behavior, scope, authority, evidence and output requirements.
  2. Shared methods: GTM research, economics, experiments and templates; no private brand records.
  3. Brand capsule: source-linked narrative, specific claims and commercial status.
  4. Current evidence: approved market/customer summaries, product acceptance and metrics for the exact task.
  5. Decision and experiment log: what changed, why, owner, version and next test.

A context file can describe a control but cannot enforce it. Review reminders are task-driven, not created schedules.

Authorization boundaries

Send — disabled

No messaging connector is established and no sending authority has been granted. Outbound assets are DRAFT only.

Requires: Explicit owner authorization naming brand, audience, channel, message version and volume; a tested connector with recorded account and scope; destination-side verification.

Publish — disabled

No publishing authority exists and no claim, offer or price is approved. Landing and ad copy remain DRAFT.

Requires: Approved claims in the ledger for the exact audience, approved offer terms, owner sign-off and a tested publishing connector.

Schedule — disabled

A template cadence (e.g. the weekly review format) is not schedule authorization. This workspace creates no recurring work.

Requires: An explicit request for a recurring task with scope, owner, destination and stop condition.

Spend — disabled

No budget is approved and no payment authority exists. CAC and economics are UNKNOWN for every brand.

Requires: An approved budget cap tied to a specific experiment card, a named owner, a stop rule and payment authority.

Export Customer Data — disabled

This workspace holds no customer records. Customer data belongs to its originating brand and purpose.

Requires: Data-owner approval, a documented consent/purpose basis, classification and retention boundary — and never across brands without an explicit, permitted transfer.