14 · Canned Responses (Objection Handling Table)

HIFI PROTOTYPE · Section 14 · Tier 1live

Purpose: Render the ≥10-objection handling table: What They Said / What They Mean / Reply.

Inputs → Output

Sources

SPP4.d6

Reads

block_g.objection_logblock_c.social_proof

Writes

objection_table

Pipeline

Load anchors

SP loaded as system message (voice anchor, Rule 4). Task prompts: SP · P4.d6. Pull ≥3 reference IDs (Rule 2). Reads locked upstream: 24.

Generate

Table of (What They Said / What They Mean / Reply), ≥10 objections

QA gate

Section 25 auto-runs QA L1 (24 checkpoints) + L2 (6 brand gates). Any L2 fail = REJECT → rewrite.

Render + ship

Sync to brand.assets. POC approves in portal → /api/brand-os/approve writes the asset → ships to domain.

Technical Reference

Generation contract (machine-executable)

section: "14"
id: s14-objection-table
state: HIFI_PROTOTYPE
tier: 1
sources: ["SP", "P4.d6"]
inputs:
    - block_g.objection_log
    - block_c.social_proof
output: "Table of (What They Said / What They Mean / Reply), ≥10 objections"
cascades_from: [24]
cascades_to: []

Supabase sync map (from Part 10)

Section 14 ->
  brand.assets where type='objection_table'

SCHEMA NOTE: verify all jsonb paths + brand.assets type values against live Supabase before write. Flag missing columns in the PR; never create new columns without review.

Note

This is a HIFI artifact: its consumer is a real customer. It only renders content that already passed the LOFI gate upstream — it never invents facts. Source of truth: Master Template Part 3 + the Master Index. To change this page, edit content/docs/roadmap/_sections.json and re-run the compiler.