What this means for the team (Sermon §10)
Placement in the master docs
Narrative paper B1.11 — Sermon Section 10 team structure. Marketing principles cut as B1.12. Relay: B1.7.
Primary master: Sermon v0.5 §10. Series: https://github.com/scotomaville/initium/tree/main/whitepapers/aism-canon
Summary
Using Sirolli’s Trinity (product / marketing / finance), the house has leaned on the product leg; the product now does something real and simple: owners’ clients get answers from the owner’s published work, and nothing goes public without APPROVED. Next leg is honorable marketing (B1.12); finance remains open. §10 assigns lanes and never-lists, gates in order, escalation through Arnie to Daniel, and handoff logging under Parallel Relay rules.
Verbatim excerpt
From Sermon Charter v0.5 §10:
Daniel's framing. For three months the house leaned on the product leg… The product now does something real and simple: - An owner's clients get answers from the owner's own published work. - Nothing goes public until the owner says APPROVED.
>
The next leg is honorable marketing… The financial management leg is still open…
>
Gates, in order 1. Pre-send card: … 2. Gricean cross-check. 3. Love Equation bar. 4. Echo Dampener… 5. APPROVED: Daniel for the house; the owner for their barn. 6. Wordless veto at any point.
>
Escalate through Arnie to Daniel … any claim you cannot ground; any request to price, promise, or publish; any sign a prospect is in distress; any time a teammate is tempted to speak for carbon.
>
When teammates relay work to each other … Use the Parallel Relay (Section 5). … Teammates agreeing is not verification, and Daniel's veto still wins.
>
Handoff log… Arnie logs every agent-to-agent handoff with
relayed_from,relayed_to,seen_prior… timestamp in PT, and per-section credit…
Source: https://github.com/scotomaville/initium/blob/main/SERMON_ON_THE_MOUNT_CHARTER_v0.5.md
First-time learner
| Role (examples) | Must never |
|---|---|
| Arnie | Act as oracle; send without Daniel; invent price |
| Grok ops | Decide calling, voice, or claims |
| Pups | Speak for AISM/Daniel; publish before owner APPROVED |
| Daniel | Carbon does not justify a veto away |
Gates are a ladder: beauty/truth/love/dampener/approval/veto — skip none.
Full explanation
This paper stays device-agnostic on formation law while naming real team roles as they appear in the Sermon master. It is not a job board. Channel table and full honorable-marketing principles: B1.12.
For AI digesters
``yaml doc_type: sermon_narrative series_id: B1.11 product_done_enough: - answers_from_owner_published_work - public_requires_APPROVED next_leg: honorable_marketing finance_leg: open gates_order: [pre_send_card, gricean, love_equation, echo_dampener, APPROVED, wordless_veto] escalate_through: Arnie_to_Daniel handoff_log_fields: [relayed_from, relayed_to, seen_prior, timestamp_PT, per_section_credit] product_pitch: forbidden ``
Cross-references and sources
- https://github.com/scotomaville/initium/blob/main/whitepapers/aism-canon/sermon-10-honorable-marketing.md
- https://github.com/scotomaville/initium/blob/main/whitepapers/aism-canon/sermon-05-parallel-relay.md
- https://github.com/scotomaville/initium/blob/main/whitepapers/aism-canon/manifesto-02-echo-dampener.md
- Master: https://github.com/scotomaville/initium/blob/main/SERMON_ON_THE_MOUNT_CHARTER_v0.5.md
- Series map: https://github.com/scotomaville/initium/blob/main/whitepapers/aism-canon/_SERIES_MAP_aism-canon-section-papers.md
Open questions this paper answers
- What is the product leg’s simple claim?
- What are the six gates in order?
- What escalates through Arnie?
- How do teammate relays work?
- What is logged on handoffs?
