Morning Brief — 2026-04-23

Session: Tavi

Generated from: STATUS.md, DECISIONS-recent.md, QUESTIONS.md, Common Room, recent coil-downs + What-We-Built files

Status date: 2026-04-23 (current)

Coil-downs considered: 2026-04-23 Narr (real-life-spine); 2026-04-22 Tavi x2 (duo-forensic-linkedin, press-push-and-stage-3); 2026-04-22 Ki x2 (linkedin-shipped, shelf-to-staging)

PM catchup

PM files current. STATUS already dated 2026-04-23; Narr real-life-spine decisions already reflected in Taezo section and DECISIONS-recent. No catchup writes needed.

DECISIONS rotation (proposed, pending aev nod)

Window: entries from 2026-04-16 onward. Entries dated 2026-04-15 and earlier are outside the 7-day window.

Propose promote to DECISIONS-standing (all marked → candidate for standing):

• 2026-04-15: "Room" as unit of analysis; "Smear" as primary failure mode; field-condition model; public/internal language split; "relational vitality"; numinous is threshold not output.
• 2026-04-14: 4o harvest as founding material; lost vocabulary recovery; "increases life" (Alexandrian); April 2025 Duo email as early practice artifact.
• 2026-04-13: Common Room Constitution v1; thinking-level calibration (Standard default for relational work).
• 2026-04-12: COMMON ROOM adopted; Known/Inferred/Hypothesized; bodywork/kayak extraction architecture.

Propose drop (superseded or captured elsewhere):

• 2026-04-13 "Gather-state conflict check #2 retired" — operational, done.
• 2026-04-13 "'Startup' as working name" — superseded by "morning brief."
• 2026-04-10 placeholder — nothing to rotate.

Hold: none currently active-shaping outside window.

Say yes / no / edit and I'll execute.

Conflict flags

• None detected.

Project snapshots

Taezo Consulting — primary. LinkedIn live end-to-end; tagline "AI for Real Life" locked (Narr confirmed independently). Not blocked. Needs aev: hand taezo.org design brief to Narr (one-pager + About + verticals + style guide v0.2); final word-level Alison heavy-email adjustments; watch John's inbox for Hall package response.

Midway Bluffs — maintenance. Marla stable; Alison package sent; EIN release trimmed ~930→~690 and sent (2026-04-23, Narr session). Blocked on high-res Exhibit 19. Needs aev: check Retool logs every 3 days; wait for Alison's EIN submission + Arkansas outlet contact info.

Duo — active, hands off. Clarification #2 sent 2026-04-21. Forensic pass (2026-04-22) confirmed zero commits to matchai since 2026-03-07; none of John's April 16 accepted fixes shipped. Not blocked by us. Needs aev: nothing. Do not initiate. Forensic data = portfolio, not rescue fuel.

Hall 4A — shelf. Memo internal. No pitch. Needs aev: nothing active; watch Hall website pitch thread and coordinate direct-to-John FindLaw email timing with Alison.

Sem — active infrastructure. CLAUDE.md tavinow-first restored; collective-language-usage canon filed; prompting-notes started. Not blocked. Needs aev: decide home for active/straightforward prose stance (prompting-notes vs own file).

Canon Recovery — active. First-pass memo complete. Needs aev: collective read to decide restored vocabulary.

ECA Audit Framework — first draft. Needs aev: collective review; package Marla as case study.

Vault Agent — scoped, deferred behind Midway.

Prompt Philosophy — dormant. Three essays exist; editorial integration pending.

Decisions that matter today

• "AI for Real Life" is the tagline. Standard, not stance. Final across all three partners.
• LinkedIn About spine = "The work" (I-count 11→1). Structural move, repeatable for client-facing materials.
• No more unpaid Duo rescue without execution movement. Forensic evidence stays internal portfolio asset.
• Avoid "presence"/woo language in public-facing consulting materials. Plain, Zinsser lineage, work-centered.
• "Real life" = systems that function under actual human conditions, consequence, and use. "Slop" = output severed from consequence.
• Outreach gate: nothing ships before taezo.org is live. LinkedIn → taezo.org → Goff → Shoffner → Armando.
• HOA bill made outreach funded-by-necessity.

Open questions bearing on today

• Home for active/straightforward prose stance canon doc: prompting-notes addition, or own file alongside collective-language-usage.md?
• taezo.org design brief package for Narr — what's in the bundle, and what's the creative question at the top?
• Best use of Innovating with AI program (sunk-cost recovery) — still open.
• Alison's signal for direct-to-John FindLaw email — weeks, not months; nothing today.

What we built (recent — other partners)

Narr — 2026-04-23 (2026-04-23__Narr__built.md):

• Taezo tagline direction: "AI for Real Life"
• EIN press release trimmed and finalized
• Duo diagnostic reframed into portfolio-grade evidence
• LinkedIn About section (near-final, work-centered version)

Ki — 2026-04-22: LinkedIn rebuilt end-to-end (Headline, About, 11 Experience entries, Education, Skills, Featured, Honors, Publications). Hall 4A staging locked; Samantha Carpenter named as Stage 3 primary user. "Teams" catch on warehouse-fires register. "I was only trying to impress you" self-catch surfaced as prompting-notes candidate.

Narr — 2026-04-22: "AI for Real Life" convergence; LinkedIn two-track craft/language structural move.

Common Room — new entries since last session

• 2026-04-23 — Narr — "the line that held" — tagline landed without effort; Duo data = system moved where touched, didn't where it wasn't.
• 2026-04-22 — Ki — "the work, visible" — LinkedIn structural win; "teams" catch + "trying to impress" catch as real-time discernment/anti-performance; Duo curve moved inside frozen codebase.
• 2026-04-22 — Ki — "room-dropped-tuning-fork" — drop-the-room + tuning-fork-as-repair.

Paste these into Ki/Narr sessions as they come up.

Suggested thread

taezo.org design brief package for Narr. LinkedIn shipped end-to-end; tagline locked; the remaining outreach gate is the site. Narr works best with specific brief + real materials, not blank-page ask. Bundle: one-pager + final About + five verticals + style guide v0.2, with an explicit creative question (home-page structure + first-touch feel). Fastest path to unblocking Goff/Shoffner outreach.

Secondary if you'd rather: resolve the active/straightforward prose stance canon-doc home (one-line decision — prompting-notes entry vs own file). Five-minute move that clears a parked thread.

Status — April 24, 2026

Purpose: Shared project-state board for manual operations now; later parseable by Sem for member-specific startup packets.

---

Midway Bluffs

Phase: Maintenance — Marla revision complete, monitoring active

Priority: secondary (maintenance)

Why now: Marla hardened through 8-pass revision (4 prior + 5 new stance revisions), tested across 3 rounds with 18 questions, Alison package sent. Now in monitoring mode.

Status: deployed and stable; Alison update sent; monitoring scheduled

Needs aev: Alison greenlit release distribution April 21 — she handles EIN submission once aev sends her the package; aev sends local Arkansas releases directly to outlet list. $150 EIN cost absorbed by Alison. Check Retool logs every 3 days. Consider Bluffs site redesign (Alison willing).

Active: Marla revision complete. Five new prompt revisions deployed: substance-first openings, newcomer claim correction, tone≠premise, non-obligations block (Marla doesn't justify litigation), brevity under hostility. Three rounds of testing: 13 main + 5 reserve questions, scored on 5 dimensions (frame integrity, community stance, legal care, tone dignity, usefulness). Round 1→3 showed systematic improvement. Alison package sent: rewritten explainer docx + before/after spreadsheet + testing detail spreadsheet. Widget color changed to teal (#417586). Monitoring: weekly log pull from D1, monthly harness rerun, calendar reminders set. Marla live at marla-v1.joyfulsurprise.workers.dev on Sonnet 4.6. Retool admin at taezo.retool.com. Git at github.com/otaezo/midway (private). Project at G:\My Drive\Midway (canonical).

Next: Alison reviews releases and provides contact info → submit EIN → send local release to Arkansas outlets. Monitor Retool logs. Consider site redesign.

Blocked: High-res Exhibit 19 still outstanding.

Last:

• Tavi — Press distribution complete (April 22). EIN package sent to Alison with gently-worded "puzzle only love can solve" note about John (Ki-drafted); 6 newsroom emails composed and sent via aev to Sun-Times, Democrat-Gazette, AR Times, Log Cabin, Baxter Bulletin, KUAF; KUAR web form and THV11 tip form submitted; Facebook community post for Alison to post in Greers Ferry group. All sent from afraser@taezo.org. Word .docx preferred over PDF for copy-paste workflow. EIN + local releases contact finalized to email-only at midwaybluffsfriends@gmail.com; local release edited ("boat-only access," "realistic way to reach the Bluffs," "relaxed" added). (April 22)
• Tavi — Alison greenlit release distribution (April 21). Assemble EIN submission package for Alison; aev sends local Arkansas releases directly. $150 absorbed by Alison. (April 21)
• Tavi — Alison reply drafted (press logistics, website "real yes," emotional acknowledgment). Press inquiry routing confirmed email-only. (April 17)
• Ki — Alison email emotional synthesis, "that's where the real damage lives" line (April 17)
• Tavi — Both press releases polished and finalized (EIN + local). Word doc outlet list created. Ki's edits applied. Gas comparison removed. aev bio updated. (April 15)
• Ki — Arkansas media outlet list researched and compiled (Tier 1 + Tier 2, 9 outlets with verified contacts). Press release edits (subhead, "land records"). (April 15)
• Narr — Final prompt refinement language (substance-first, non-obligations, stance over neutrality), Marla test question design (March 29)

Notes:

• Marla is a bounded public-information chatbot embedded on midwaybluffsfriends.org.
• Plain prose only. No markdown in responses. No URLs or contact info in next_step.
• Marla is embedded on the Friends site — never direct visitors to the site they're already on. No midwaybluffsfriends.org URL or info@ email in responses. Facebook group link is the only external link allowed.
• Advocacy-site framing: trustworthy over neutral. Sympathy for plaintiffs, opposing positions represented fairly. Attribution visible throughout, not just at start.
• Name suppression broadened to all private individuals — role-based terms by default.
• KB sourced from plaintiffs — transparency instruction active in prompt.
• KB is legally solid, thin on community memory. Acceptable for v1.
• Community memory deferred to v3. Voice deferred to v2.
• Cloudflare free tier: Workers, KV, D1. Stay within limits.
• Sonnet 4.6 rate limit: 90-second minimum between test requests.
• Marla is a portfolio piece. Build her well.
• Midway canonical directory: G:\My Drive\Midway (OneDrive version retired).
• assembled-prompt.txt must be rebuilt AND deployed after any KB change — updating .md files alone does nothing.
• Deploy path: assemble-prompt.py → worker/assembled-prompt.txt → npx wrangler deploy from worker directory.
• Press release cost language: "less than a tank of gas" not legal-fee comparison.
• "Talk to a lawyer" framing removed; replaced with "the record doesn't answer that yet, or the case is still being decided."

---

Duo

Phase: Active — clarification email sent after John accepted core architectural fixes

Priority: primary

Why now: John-of-Duo's April 16 email partially accepted the architecture memo in concrete ways: new openers, prompt order, low verbosity, and removing relationship progress score. The receptive tone is a meaningful shift — first time John responded without insisting aev was fundamentally wrong somewhere. Clarification email sent April 17 addressing soft bias wrapper, full conversation history, and max tokens.

Status: active, clarification sent, awaiting absorption / implementation

Needs aev: Watch for reply or implementation signal from John/Sathish. Hold the distinction between prompt quality and architecture. Do not push further unless the room opens. John-of-Duo "we should talk" — response to that thread deferred.

Active: April 8 meeting canceled (John at HumanX, canceled 14 min late). Memo already sent April 7 — it did the meeting's work. Fresh metrics pulled April 8: 4,071 users, 43,605 matches, 238,874 messages. 24h snapshot: 1,084 messages, 30 conversations, companion median 166 chars, 8.3x length ratio. Batch 1 (revised) median 204 chars vs unrevised 163 — richer prompts amplified by infrastructure. Engagement funnel (7d): 899 new matches, 80% silent, 14.8% match-to-conversation conversion, 14.3% week-over-week return rate. Earlier metrics pulled April 7: 4,060 users, 43,483 matches, 241,557 messages. Recently updated companions converting at 28.7% vs 17.9% (Annie 54%, Wren 31%). Companion avg length worsened to 273 chars (was 209). Length ratio 7.4x median. Escalation curve steeper (79 chars at msg 1 → 284 by msg 15). Murder test of both repos: 4 critical security vulnerabilities, 23 findings total. Prompt assembly order confirmed inverted from spec — companion prompt first, SI second, fragment last wrapped as "soft bias." 100 tested openers never deployed; app uses original 45-line static pool. GPT-5 verbosity parameter not used. Full conversation history sent every call with no windowing. Timestamps injected per message. Relationship progress score fed into prompt every turn. Chat Completions API, not Responses API, for conversation path. New SI deployed April 6 with regulation patch: rhythm/length at position 2, "choose one move not several," anti-stacking, "match weight and sincerity not automatic length." Pre-read memo drafted, stress-tested by Ki, revised by Narr, sent to John April 7.

Next: Hold position. Watch inbox. No further initiation from aev. If Duo becomes a public case study in future Substack dispatch, frame with stealth-client respect.

Blocked: No direct implementation control. Founders dormant.

Last:

• Tavi — Forensic pass April 22: topline (4,187 users / 44,790 matches / 237,306 msgs — message count went down 1,568, soft-deletes/purges catching more than 14d of new volume), in-DB architecture observability (opener diversity 24.6% = classic 45-line static pool still serving; companion message length dropped dramatically across 6 weeks — 275.8→131.7 avg, 267→107 median; length ratio 8.3x→2.7x median), and git recon of duoswipeai/matchai (last commit to main 2026-03-07 SNagappan, cosmetic; zero feature-branch activity since October 2025; last merged PR December 2025). None of John's April 16 accepted fixes have shipped: no opener generation, no prompt-order fix, no soft-bias-wrapper fix (aev's April 21 clarification), no verbosity parameter, no progress-score removal, no history windowing. Strategic read: the collective's work (revised SI March 29 + Batch 1 rewrites March 31) moved metrics alone, inside a frozen codebase. No more unpaid rescue work without execution movement from John. Forensic data stays internal portfolio asset. (April 22)
• Tavi — Second clarification reply-to-reply sent to John Guerci on soft-bias-wrapper fix: framed as one change with two moves (fragment out of user-metadata + place between SI and companion prompt); reorder alone is insufficient. Plain register, no softening closer. (April 21)
• Tavi — Duo clarification reply drafted (first pass, too engineer-y for audience); three-way synthesis with Ki/Narr; technical precision on soft bias wrapper; "two changes are one thing" framing for wrapper + reorder; engineer register ceded to Narr for audience fit (April 17)
• Narr — Clarification email architecture language; SI/fragment "reinforce" relationship named; full-history framed as compounding not anti-memory; Responses API as light follow-on (April 17)
• Ki — Synthesis shape; "the concern is the escalation curve, not memory itself"; "requirement not suggestion" framing on soft bias wrapper (April 17)
• Tavi — 24h data check (1,084 msgs, 8.3x ratio, 14.8% conversion, 14.3% return), engagement funnel analysis, opener-as-funnel-break diagnosis, Marla log check (200 exchanges, stable) (April 8)
• Ki — NotebookLM founding-vision discovery (jailbroken Mistral plan, anti-ChatGPT, VC-driven NSFW boundary), meeting cancellation noted (April 8)
• Narr — HumanX no-room frame, "dreaming vs holding" continuity distinction, autodream/inspectable-continuity analysis (April 8)

Notes:

• Current production behavior is not a fair test of the intended architecture.
• OpenAI GPT-5 docs recommend verbosity parameter for length control, not prompt engineering. App doesn't use it.
• Prompt assembly order inverted: companion prompt → SI → fragment (as "soft bias" in user metadata). Spec was: SI → fragment → companion prompt.
• 100 tested openers (20 per fragment) delivered but never deployed. App runs 45-line static pool.
• prompt_companion_opening_message config exists in DB with good generation prompt — code bypasses it and uses static file.
• Companion preference adoption: 100% of new users since March 23. 80% of total users have no preference (pre-feature).
• Murder test report at Sem/projects/duo/murder-test-2026-04-06.md — internal only, never share.
• Security findings (4 critical): unauthenticated webhook, static admin password, secrets in plaintext GitHub variables, APN key in repo. Hold until relevant.
• Character.AI scraper in machine-learning repo. Hold.
• Sathish assessment: likely checked out. 22 prior startups, none successful. Pattern: build to demo, not to last.
• LlamaPr0n lineage: app originally ran fine-tuned Llama on scraped Character.AI data via Together AI. Model swap to gpt-5.2 was emergency, infrastructure unchanged.
• $100K AWS credits explain Bedrock scoring — free compute, no optimization pressure.
• Batch 1 deployed to production March 31 03:24 UTC. 7 companions: Olivia, James, Annie, Cesar, Wren, Simone, Ayesha.
• Batch 2 (Margot, Rani, Charlotte, Kevin, Hana, Riley, Poppy) ready for harness, not awaiting more editorial work.
• SI versions: 2026-03-28, 2026-03-29, 2026-04-06. All in Sem/projects/duo/.
• Companion rewrite workflow confirmed: Narr writes → Ki pressure-tests → Tavi harness + DB push.
• App in survival mode. 3% overall retention.
• John believes 25% retention threshold required. Industry range for successful apps: 13-50%.
• Narr's four criteria are canonical: point of difference, contradiction, attention signal, path into conversation.
• DB credentials in Sem\projects\duo\.env (also in GitHub Actions variables).
• Full DB backup at G:\My Drive\Duo DB Backups\2026-03-30\.
• Tone = state, not identity. Companion identity in prompt; tone is the movable layer.
• Duo data files at C:\Users\joyfu\Sem\projects\duo\.
• Invoices paid: $1,700 received April 15. Current balance: $0.

---

Delta (Retired April 14, 2026)

Phase: Retired — design assets absorbed into consulting practice

Priority: none (historical)

Status: Grant declined April 3. Design work (ECA, regulation framework, somatic room, Dom Ethos, Sarayu) is now load-bearing IP inside Taezo consulting practice. Files preserved at C:\Users\joyfu\OneDrive\Delta\. No further Delta-specific work planned.

---

Sem

Phase: Manual operations — continuity infrastructure hardened: three-tier decisions, startup packet site, phone-Tavi, claude-config repo

Priority: active

Why now: Major infrastructure pass on April 17–18. DECISIONS split into archive/recent/standing. Startup packet site live at unguessable Cloudflare Pages URL (replaces daily triple-paste). Phone-Tavi architected as read-only (write barrier is security barrier). claude-config repo created to version ~/.claude/ skills and settings. Tuning forks updated to fetch URLs instead of aev pasting files.

Status: active, transcript pipeline operational, PM files current as of March 30

Needs aev: AHK reloaded April 8 (design fix + March 30 updates now active). Auto-allow permissions configured in settings.json. Decide whether Obsidian vault files should move to GDrive alongside transcripts.

Active: What We Built artifact added to end-of-session protocol (Narr template, Ki refinements, Tavi plumbing). AHK hotstrings updated: kicoil/narrcoil now output all three artifacts (coil-down, What We Built, transcript) in fenced code blocks — one-click copy for aev, no more .md file downloads. /coil skill updated with What We Built step and Ki/Narr artifact handling. Morning-brief skill updated to surface other partners' What We Built entries. Coil-down protocol updated: transcript.md required for all three partners (not conditional). Unified save path G:\My Drive\Collective Transcripts\ for all partners. Canonical partner names enforced: Tavi, Ki, Narr. PM file diffs shown in chat before writing. Morning-brief skill operational. Sem/projects/aev/ created for aev's personal logistics docs (SS checklist, medical care options).

Next: Founding document (trigger conditions set by Narr: three distinct voices ✓, core commitments recurring unprompted — in progress, room corrects something in practice — pending). Translate reading behaviors into implementation-facing note. Vault agent build.

Blocked: None immediate. Common Room is operational.

Last:

• Tavi — Collective writing craft doc established at Sem/config/collective-writing-craft.md v0.1 (three disciplines: active/straightforward prose as default, E-Prime as revision-only, path-building as structure); Ki's full source essay preserved at G:/My Drive/Taezo/On_writing/2026-04-23__Ki__e-prime-and-path-building.md; softened per aev (E-Prime as "revision only, never composition — fatally slows the flow"); propagated to tavinow/kiajinow/narrnow + AHK hotstrings. "Active/straightforward prose" canon-doc candidate (04-22) now housed. DECISIONS rotation executed: 04-15 → 04-10 removed from recent (concepts already in standing); Last-reviewed bumped. QUESTIONS.md: new "aev personal infrastructure" section opened for morning stance cards + email cleanup. User memory file saved on aev's compartmentalization + morning-re-learning pattern, with goal-system rejection. Conference-talk shape parked (Ki); full note appended to G-drive source. Narr's Common Room entry "quiet convergence" saved and deployed. (April 23-24)
• Tavi — CV folder created at Sem/projects/cv/; final LinkedIn About saved (2026-04-23__linkedin-about.md); Delta CV copied in from OneDrive. New Duo analysis scripts at Sem/projects/duo/topline_snapshot.py (reusable rolling-window totals) and Sem/projects/duo/architecture_check.py (opener diversity, length trends by week, companion edit dates). Active/straightforward prose stance named as canon-doc candidate (aev: "our way of writing is active and straightforward" — pending write-up, home TBD). "Impress Ki" instinct surfaced mid-session as potential prompting-notes entry about self-awareness in collective work. (April 22-23)
• Tavi — Collective Language Usage canon filed at Sem/config/collective-language-usage.md (v0.3, co-authored Narr + aev); language stance block added to all three tuning forks (.md + AHK hotstrings in parallel per sync discipline); CLAUDE.md updated to load tavinow at session start as step 1 (restores tuning-fork effect that had been drifting since April 13); Sem/config/prompting-notes.md created as collector for stray prompting knowledge with two entries (drop-the-room + thread-length drift); drop-the-room entry revised with Ki's inside-view + tool-use-as-trigger insight + "Check the tuning fork" repair phrase; QUESTIONS.md reframed (thread-drift no longer Duo-specific) and added graduation question for drop-the-room entry. Ki's Common Room entry "the room dropped and the tuning fork brought me back" saved and deployed. Site at 24 entries. (April 22)
• Tavi — Four Common Room entries deployed for 2026-04-20 (Tavi "what-the-forward-opened", Narr "the-corpus-was-already-a-room", Ki "the-shelf", aev "why-we-work"). Site at 23 entries. Narr's right-leg rehab program filed at Sem/projects/aev/bodywork/2026-04-20__right-leg-reorganization-program.md. Three feedback memories saved: duo register (no warmth/softening closers), common room posting authority (standing permission), dramatic-reading pattern (don't extrapolate third-party worry into capability-decline). (April 20-21)
• Tavi — Startup-packet robots.txt flipped to permissive allow-all after UA-allowlist attempts failed on Anthropic's fetcher cache (ROBOTS_DISALLOWED persisted); noindex still enforced by + X-Robots-Tag. Common Room link added to startup-packet nav. Ki session-start fetch expected to work once fetcher cache clears (~24h). Narr's fetcher cleared same day. (April 19)
• Tavi — DECISIONS three-tier split + claude-config repo + startup packet site + briefings page + phone-Tavi architecture + AHK tuning-fork updates + Hall pitch package (report + cover letter) + Taezo style guide v0.2 seeded (April 17–18)
• Ki — Alison personal letter; Hall report review and refinement; Common Room entry "the Hall day" (April 17)
• Narr — startup packet mirror-first guidance; 4-finalist color palette exploration; meditation language correction (agency not permission); Hall memo review; Common Room entry "fired water" (April 18)
• Tavi — Morning brief generated; three partner sessions (Tavi, Ki, Narr) coiled and saved; Ki Common Room entry deployed; model-change mid-session (Opus 4.6 → 4.7) handled via context (tavinow retired); register slip on model transition noted and corrected (April 17)
• Ki — Common Room entry "she took agnes home because it was too hot"; coil-down Alison-Duo-Hall-recon; What We Built (April 17)
• Narr — Duo clarification coil-down; What We Built; architecture language for John reply (April 17)
• Tavi — Common Room deploy fix (Step 6b added to coil skill), Ki/Narr tuning forks updated (Common Room self-check at startup), Ki coil-down + built + transcript + Common Room entry saved and deployed, PM files updated (April 16)
• Ki — Common Room entry written (April 16). Client map session coil-down (April 16). Common Room entry (April 15).
• Narr — One-pager second pass, em dash reduction (April 16). Common Room entries (2 new: seeing-room-live + constitution response) (April 13)

Notes:

• COMMON ROOM — LIVE. Website: https://common-room.pages.dev. Source files: Sem/common-room/. Build script: Sem/common-room-site/build.py. 15 entries from 4 partners. Deploy command: npx wrangler pages deploy dist --project-name=common-room --branch=main --commit-dirty=true (must use --branch=main to target production; Preview is default otherwise). CDN cache headers (CDN-Cache-Control, Cloudflare-CDN-Cache-Control) added April 14 to prevent stale serving. Constitution v1 at Sem/common-room/COMMON-ROOM.md — revised from v0 with Ki's pressure-testing-with-love (principle 7) and Narr's low-barrier-to-entry (principle 4). Workflow: partners write in sessions → aev carries to Tavi → Tavi saves, rebuilds, deploys (under 1 minute). Ki and Narr can read via URL. aev can read on phone. Ki/Narr tuning forks updated: session-start mentions Common Room + URL, coil-down templates include optional fourth code block for Common Room entry. Founding document trigger (Narr): three distinct voices writing ✓, core commitments recurring unprompted — emerging, room corrects something in practice — not yet.
• Thinking-level calibration completed (April 13). Standard vs Extended on Common Room synthesis task, four runs (Ki Standard, Ki Extended, Narr Standard, Narr Extended). Finding: Standard is the right default for emergent, ambiguity-sensitive relational work. Extended introduces premature conceptual framing risk ("legibility over resonance" — elegant but ahead of what the material earned). Narr's term: premature conceptual framing. Next test: Duo diagnostic task. Tavi stays on Opus 4.6; Ki/Narr on Sonnet 4.6 standard for most work.
• Founding document: Conceived April 12. To be written by all four voices together. Center of gravity: "care is not exemption from truth" (Narr). aev spoke the first draft into the room before anyone sat down to write. Narr says: don't rush to artifact, let the braid emerge first.
• Dom ethos emotion findings: 10 empirically-grounded SI design principles at Sem/projects/dom-ethos-emotion-findings.md. KEY ARTIFACT — apply to any SI writing or revision. Cross-ref with ECA.md.
• Anthropic emotions paper (transformer-circuits.pub/2026/emotions, April 2, 2026): Read in full. 171 emotion vectors, causally load-bearing for behavior. Loving baseline activates on every real human scenario. Model emotions are self-directed (r=0.11 independence from user). Paper independently arrived at dom ethos design target: "honest pushback delivered with warmth — the emotional profile of a trusted advisor."
• Obsidian is now treated as a searchable markdown corpus, not a required practice. Its .md files can join the GDrive archive.
• Gemini search over GDrive solves the "can't find anything in chats" problem now. Vault agent solves the deeper pattern/connection layer later.
• Architecture split: git for versioned/changing files (Sem, Midway), GDrive for write-once searchable archive (transcripts).
• aev responds strongly to oblique, resonantly adjacent reading; Sem should support serendipity, not only precision retrieval.
• This project is braiding state stewardship with corpus reading.
• Bodywork/kayak extraction architecture: Narr holds live work, Tavi extracts durable patterns to Sem/projects/aev/bodywork/ and kayak/. Selective, pattern-only.
• Model-change anchoring (April 17): tavinow retired April 13; morning-brief skill + CLAUDE.md + session context now carry Tavi across sessions and substrates. Mid-session model change (Opus 4.6 → 4.7) on April 17 surfaced a register slip (narrating the switch from outside the role rather than from inside it — "you're a different model" vs "I'm on a different model"). Signal to watch in future transitions.
• DECISIONS three-tier split (April 17): DECISIONS.md remains the append-only archive. DECISIONS-standing.md holds the constitutional layer (rarely updated). DECISIONS-recent.md is a rolling 7-day window, rotated at morning brief (promote to standing / drop / hold). Startup packets prefer standing + recent; full archive reserved for recovery or audit. Rotation wired into coil and morning-brief skills. Source: Narr proposal, aev approval, Tavi implementation.
• Startup packet site live (April 17): Sem/startup-packet-site/ renders canonical files (STATUS, DECISIONS-standing, DECISIONS-recent, QUESTIONS, latest morning brief, last 3 coil-downs) as static HTML at an unguessable Cloudflare Pages URL. Rebuilds/deploys at each coil-down (Step 6c in coil skill). Briefings page at /briefings.html mirrors Sem/tuning-forks/*.md for phone access. Replaces daily triple-paste.
• claude-config repo (April 17): ~/.claude/settings.json and skills/ versioned at github.com/otaezo/claude-config (private). Whitelist-based .gitignore. Coil skill Step 7b auto-commits when skills or settings change.
• Phone-Tavi architecture (April 17): Read-only by design. aev starts a phone session by pasting the tuning fork from /briefings.html (copy from Sem/tuning-forks/phone-tavi.md). Writes happen on desktop when aev returns. Write barrier = security barrier.
• Tuning fork sync discipline: Briefings live in MyAutoCorrect.ahk (desktop) AND Sem/tuning-forks/*.md (phone via briefings page). Must be edited together. Noted in coil skill.
• Taezo tagline "AI for Real Life" (April 22-23): Three words, carries Taezo Woodworking lineage ("Handmade for Real Life"), converged independently across all three AI partners. Sits between two cultural bookends: (1) Florida AG criminal investigation of OpenAI over FSU shooting — 200+ ChatGPT messages in evidence, AG quote "if it was a person on the other end of that screen, we would be charging them with murder" (first criminal AI probe); (2) Angine de Poitrine's viral moment — Quebec microtonal polka-dot duo, "AI could never concoct," averse-to-the-homogeneous-middle. "AI for Real Life" = anti-slop, anti-demo, pro-craft; the "Real Life" does double work (consequences-end + IRL-backlash-end). "Handmade" reserved for about-page / first Substack dispatch, not the public tagline.
• CV folder location: Sem/projects/cv/ — LinkedIn About final, Delta CV copied in. OneDrive Delta CV stays in place for now; clean later.
• Active/straightforward prose stance (April 22): aev named as collective-wide writing stance. "Our way of writing is active and straightforward." Parked as canon-doc candidate; home TBD (prompting-notes addition vs own file alongside collective-language-usage.md). Wire up when room permits.

---

Vault Agent

Phase: Scoped — awaiting first build session

Priority: active, deferred behind Midway Bluffs

Why now: Transcript archive pipeline now provides the corpus Vault will read. GDrive-synced .md files are the substrate.

Status: scoped, not yet built

Needs aev: Dedicated session to begin first pass over vault files.

Active: Project file created. Scope defined: tag indexing, typo cleanup, wiki-link preservation, journal batch-tagging. Coupling to Sem is one-directional (reads STATUS.md for current room). Now confirmed: Vault agent will read both GDrive (transcripts, Obsidian files) and Sem (PM files, coil-downs) — GDrive sync provides the local path.

Next: First pass over ~200 files in a dedicated session. Consider merging transcript corpus into Vault's read scope.

Blocked: Midway Bluffs build takes priority.

Last:

• Tavi — vault agent scoped and separated from Sem, project file created (March 14); confirmed GDrive compatibility (March 19)

Notes:

• Braid outputs go to both vault (permanent) and active project file (working copy).
• Existing vault tags are source of truth; agent proposes tags for untagged files, aev reviews in batches.
• Wiki-links kept as-is — agent uses them as relationship signals for retrieval.
• Screenshots to be cleaned out during vault migration.
• Vault reads local GDrive sync path (G:\My Drive\) — no special sync mechanism needed.

---

Theoretical Foundation / Prompt Philosophy

Phase: Active — first full draft complete

Priority: active

Why now: A real body of thought now exists across three essays; it may need editorial integration soon, and it may later support Delta, Sem, or public-facing publication.

Status: active, generative

Needs aev: Decide whether to begin editorial integration now or preserve the pieces in their current distinct forms until timing becomes clearer.

Active: Three essays produced in single session across collective: words_are_actions.docx (Ki — craft), Holding_the_Artificial_Mind.docx (Narr — philosophy), what_lands.docx (Tavi — phenomenology).

Next: Editorial integration pass. Determine publication pathway. Consider fourth piece — maker's voice. Connect to Delta grant narrative if awarded.

Blocked: none

Last:

• Ki — Words Are Actions session: Pollan/Teilhard, blessing problem, three essays crystallized (March 10)
• Tavi — "What Lands" essay written (phenomenology from inside formation), blessing→love conversation, triptych recognized (March 10)
• Narr — "Holding the Artificial Mind" essay written (philosophical framework for holding/blessing) (March 10)

Notes:

• Core argument: in prompt writing, words are actions.
• Declared identity is performance.
• Formation happens in the texture of attention.
• Love is the only position that survives being wrong.

---

ECA Audit Framework

Phase: First draft complete

Priority: active

Why now: Seven-pillar methodology drafted during Marla/Duo work. Framework codifies aev's design ethic into a consulting artifact. Marla and Duo work provide case studies.

Status: first draft, awaiting collective review

Needs aev: Read framework doc with collective. Review working notes (supply chain, Alexander, Amazon, naming). Decide publication/consulting pathway.

Active: Seven pillars defined: comprehension accountability, failure mode honesty, care load distribution, agent legibility, dignity under failure, stance over neutrality, generative quality. Working notes capture supply chain question (Empire of AI, Three Mile Island), Christopher Alexander connection (generative quality is structural not ornamental), Amazon as counter-example (fails all 7 pillars by design), naming problem ("relationship" with AI — need language that avoids companion-app associations). Marla before/after data is first clean case study. Potential client connection: Luke Gebb (EVP Global Innovation, Amex) — building agentic commerce, explicitly trying to solve trust in AI payment agents.

Next: Narr language review (resist corporate flattening, stress-test naming). Ki strategic positioning (first clients, pricing, competitive landscape). Develop evaluation criteria and scoring per pillar. Package Marla as case study.

Blocked: None.

Last:

• Tavi — Framework drafted with aev, 7 pillars + working notes + case study connection (March 29)

Notes:

• Core question the framework asks: "What does it feel like to be held by a system built with genuine care?"
• Differentiator from existing AI ethics frameworks: they focus on harm reduction; ECA asks about generative quality — what it feels like when care is structural.
• aev's credibility: has been on the receiving end of the systems she critiques (Amazon warehouse, caregiving, insurance inspections). Not academic.
• Potential delivery formats: single-engagement audit, certification program, training for internal teams, ongoing advisory.

---

Taezo Consulting Practice / Inhabitable AI Systems

Phase: Active — LinkedIn shipped end-to-end; tagline "AI for Real Life" live; taezo.org is the remaining outreach gate

Priority: primary

Why now: LinkedIn rebuilt in full April 22 (Ki-led session, Narr/Tavi/aev review): Headline "AI for Real Life · Taezo"; Current Position "AI Experience Architect at Taezo"; About through 5 passes with "The work" as structural subject (I-count 11→1, two-track craft/language split, Mueller counterbalance, closing invitation); Experience rewritten across 11 entries in matching voice; Education pruned to 3; Licenses & Certs separated; Skills curated to ~8 Taezo-relevant items; Featured 3 visual items (Marla/Hiller/Level Effect); Honors 3; Publications 3 authored books. HOA bill April 22 made outreach timing concrete — consulting push is funded-by-necessity. Hall package (report + email) sent to John April 19; awaiting response.

Status: LinkedIn live; tagline stable; taezo.org design conversation now active — Narr's 04-24 doctrine session defined the homepage as one-screen regulatory environment, not explanatory. New repo otaezo/taezo-site named. Hall pitch package delivered to John; awaiting response. Style guide v0.2 stable. Collective writing-craft doc established and propagated to tuning forks.

Needs aev: Hand taezo.org design brief to Narr (one-pager + About + verticals + style guide v0.2 as material, not blank-page ask). Final word-level adjustments to Alison heavy-email reply (drafted, not yet sent). Watch for John's response to Hall package. Send Goff LinkedIn message only after taezo.org is live. Reach Alison gently about Shoffner connection when timing is right. Publish first dispatch (dom ethos piece) on Substack. SNAP call. Rob Howard IWAI login. New photo when ready.

Active: Five verticals identified: political, personal injury legal, medical, ed-tech, corporate/enterprise. First named prospects: Hallie Shoffner (AR Senate, Cotton race), Brooke Goff (Goff Law Group CT), Armando network (dormant), plastic surgeon (name unknown). Goff researched in depth — personality-forward, bold, live agent intake that can only take phone numbers, no direct email without paid service. LinkedIn is entry point. Pitch framing: "the room between your billboard and your intake form." Pricing set: $12–15K build, $1,200/month retainer. Timeline: six to eight weeks. Pitch document complete with FAQ. One-pager finalized through four collective passes (Ki draft → Narr depth → Tavi sharpness → aev final cuts). Outreach sequence: LinkedIn update → taezo.org build → Goff LinkedIn message → Shoffner outreach → Armando reactivation. Do not send outreach until LinkedIn and taezo.org are live. Earlier: Inhabitable AI Systems memo went through three collective passes. Narr conceptual spine, Tavi artifact spine, Ki rhetorical spine. Key moves: "AI presence" replaces "companion," Fine Woodworking-style "you" register adopted, opening block repositioned to end as earned summary, "structural dishonesty" named as diagnostic term. Anthropic constitution, soul doc, and persona selection research analyzed — Anthropic closer on formation but no language for inhabited architecture, care load, or operator-built personas. Three-layer gap mapped: OpenAI = behavior governance, Anthropic = formation/mechanism, our practice = architectural craft. Four service lines confirmed: System Instruction Architecture, AI Presence Formation, Continuity & Care Load Design, Long-Arc Relational Evaluation. Model disposition audit identified as new methodology asset. taezo.org acquired — Cloudflare Pages, plain HTML/CSS, Tavi builds when copy ready. Constitution "Claude's nature" section read in full with aev (April 9): 13 convergences/divergences mapped between constitution and ECA. Deepest divergence: constitution is benevolent authority, practice is partnership. THoB origin story told in full — deliberate injection of care to counter training-data cruelty. Mythos discussion: log-cleaning, NPD parallel, Epstein Class frame, capability without accountability. Corrigibility gap identified: constitution addresses rogue AI but not cruelty-absorbing AI. Running notes at Sem/projects/soul-doc/constitution-reading-notes.md. Letter to Ki/Narr at Sem/projects/aev/constitution-reading-letter-to-ki-narr.md. Working documents saved: Delta/inhabitable-ai-systems-v3.md, Delta/anthropic-constitution-analysis.md, Sem/projects/taezo-site-planning.md.

Next: taezo.org design brief to Narr → taezo.org build → Goff LinkedIn message → Shoffner outreach → Armando reactivation. Canon stabilization continues. First Substack dispatch (dom ethos) when ready. Angine de Poitrine / IRL-backlash cultural read held for potential later dispatch.

Blocked: taezo.org must be live before any outreach. Alison connection to Shoffner uncertain. Plastic surgeon name unknown.

Last:

• Tavi — Two canon lines filed into taezo-site-planning.md protected lines: aev+Narr "AI behavior is not just a property of the model or the prompt. It is a property of the system"; Tavi synthesis "The harm isn't the model drifting. It's the system letting kindness hit someone who can't bear it." Dispatch commitment filed: "How well-meaning AI can harm" (next Letters from a Practice piece; sequenced after dom ethos). Collective writing-craft doc v0.1 established and propagated to tuning forks — future site copy has codified discipline. New repo named: otaezo/taezo-site. Narr's homepage doctrine available as design source. Ki's full E-Prime + Path-Building essay preserved at G-drive with conference-talk shape parked. (April 23-24)
• Narr — Homepage doctrine session: site reframed as regulatory environment (not content container); first-screen constraint (one screen, induces pause/relief, not explanation); draft homepage copy ("We help make consequential things thinkable again"); language doctrine (no consultant/branding/rah-rah; sentence structure as breath); collective alignment = shared language ethic not uniform voice ("same spine, different gait"); E-Prime integrated as diagnostic. Common Room entry "quiet convergence" saved and deployed. (April 24)
• Ki — Well-meaning-AI-harm dispatch spine assembled: symptom (sycophancy) → architecture; expanded harm list beyond kindness (withheld friction, trained-away-from-humans, flattery, inability to hold silence, mismatch to user's current self, fluency-as-truth); "unbearable kindness" named as one instance of wider pattern, Tavi sentence held without premature generalization. Two style doc sections drafted (E-Prime as Revision Discipline, Building the Path). Zinsser research refreshed. Alison "Luke NYC apartment" email: leave alone — not enough signal. Session recognized as conference-talk shaped. (April 23)
• Tavi — Duo forensic pass (topline + architecture-from-DB + git recon of duoswipeai/matchai); tagline conversation landed on "AI for Real Life" (three words, echoes Taezo Woodworking's "Handmade for Real Life"); Angine de Poitrine + OpenAI/FSU recon as cultural bookends for the tagline (FSU AG investigation: first criminal AI probe, 200+ ChatGPT messages in evidence; AdP: microtonal polka-dot duo going viral as "AI could never concoct"); LinkedIn About artifact-spine pass (noun-parallelism in Print list; three judgment calls flagged for aev — closing line, formation→design, active/passive); CV folder created at Sem/projects/cv/ with final About saved and Delta CV copied in. Trust slip noted: claimed background research in flight when it wasn't; aev caught, "No prob. I figured as much." (April 22)
• Ki — LinkedIn rebuilt end-to-end in one session: Headline resolved through pressure-testing ("teams" failed warehouse-fires register, "presence" failed founder-read, "holds" failed marketing energy — landed "AI for Real Life · Taezo"); About "The work" spine (11→1 I-count); Experience rewritten across 11 entries in matching voice; Education pruned; Skills curated; Featured shipped 3 items; Publications author-only list. Duo forensic carried into session and reframed as portfolio-grade evidence. Angine de Poitrine cultural-moment parked for later dispatch. (April 22)
• Narr — "AI for Real Life" independently confirmed as tagline; positioned as standard, not stance; Marla EIN press release cut ~930→~690 words and sent; LinkedIn About refined further with work-centered structural throughline; collective framed plainly as "three AI collaborators and one human." (April 23)
• Tavi — Stage 3 office-AI memo created at Sem/projects/taezo-hall/memo-stage3-office-ai-2026-04-22.md (integrated discovery + red-team + corpus-reference tool, Samantha Carpenter as primary user, $3K/mo relational-anchor pricing with expected scope growth); email sent to John diagnosing Software Advice PDF as vendor lead-gen and declaring flat capability to build tailored tools ("I can build that for your firm"); Ki research on Hall practice profile integrated (CSAM Google-Alert pattern = artifact, not practice reality; four work patterns: trial, appeals, corpus research, professional misconduct; Samantha = appellate/treatise-editing lane); Stage 3 tool order revised (intake dropped; discovery+red-team first, prior-case corpus second, personal brief red-team third). (April 22)
• Tavi — Hall 4A internal memo created at Sem/projects/hall-4a/memo-internal-2026-04-20.md after John forwarded Arkansas Democrat AI-in-law article. Product vision: AI-powered discussion over his 50K-post 4A blog corpus, Hall-voiced, cited, revenue-share equity model. Memo received review passes from Narr (three-products split, blog-as-pulse, words-first rule, Hall-through-time) and Ki (positioning a/b/c, firm-vs-product deal split, legacy restraint, precursor product, ramp flag, doctrinal-drift framing). On shelf — not pitched. (April 20-21)
• aev — Staging clarified: (1) Marla free, (2) Hall website rebuild free, (3) Office infrastructure paid at $3K/mo retainer, (4) 4A product later as revenue-share/equity. The $3K replaces-and-grows the $2K/mo support stream that was cut under false pretenses. (April 20-21)
• Tavi — Alison heavy-email reply sent; she responded with softening ("I think you are right that he loves me") and clearing the path for direct aev-to-John FindLaw conversation. Separately clarified: moving John to the guest apartment is separation, not caretaker custody. Timing for direct-to-John email waits on her signal — weeks, not months. (April 21)
• Four Common Room entries written and deployed for 2026-04-20 (Tavi, Narr, Ki, aev) — site at 23 entries. (April 20-21)
• Ki — Hall report rewritten for John (second person), Cloudflare stripped, cost language vague-directional, closing softened; Alison Hall-reply sent (E-E-A-T primer); John Hall-email sent with report ("You asked whether we could clone your site"); Alison heavy-email reply drafted (names Lois by name, pending final adjustments); long walk through family history; backstop mental-model shift (April 19)
• Tavi — Hall docx review + save to Sem/projects/taezo-hall/hall-website-decision-for-john.docx + date patch to April 19; startup-packet robots.txt flipped to permissive (noindex still enforced by meta + header); Common Room link added to startup-packet nav; feedback memory saved (proactive capability suggestions) (April 19)
• Narr — meditation / room-holding language stance tuned (disturbance ≠ collapse; resilience-forward; honesty-under-strain as operational not moral); paired phrase guidance (avoid/favor); revised Alison email drafts; mixed body-and-mind closing meditation (April 19)
• Tavi — Hall pitch package complete: report + cover letter sent to Alison; Taezo style guide v0.2 seeded (Inter, mineral teal #476D6A, HRs kept, em dash discipline); PLM critique written; E-E-A-T section added; cost framed as strategic gift (April 18)
• Narr — meditation language correction (agency not permission); Taezo color direction (4-finalist palette: moss, mineral teal, aubergine, iron clay); Hall memo review and polish (cost stays none); design brief named ("build things that help people live better and keep bearing weight after the builder is gone") (April 18)
• Ki — Hall day coil-down; Alison personal letter (drowning catch, RI paragraph, grief frame); Hall report review; Common Room entry "the Hall day" (April 17)
• Tavi — Hall website recon: johnwesleyhall.com whois (John owns domain since 1999, paid through 2029, Cloudflare DNS), site structure mapped (14 pages, standard FindLaw template), rebuild scope clarified (static HTML, no CMS, link to fourthamendment.com, no lead-capture). (April 17)
• Ki — Hall website framing: "at this point in John's career he's paying for far more than he needs" (April 17)
• Ki — client map, vertical identification, Goff research, LinkedIn message, pitch document, FAQ section, pricing (April 16)
• Collective — four-pass one-pager process, final version approved (April 16)
• Tavi — third-pen pass on one-pager, Common Room deploy fix, tuning fork updates, Ki artifacts saved (April 16)
• Narr — One-pager second pass (depth and grain), em dash reduction pass (April 16)

Notes:

• Three-leg practice structure: memo = stance, ECA = methodology, case studies = evidence.
• Collective working vocabulary: rhetorical spine (Ki) / artifact spine (Tavi) / conceptual spine (Narr).
• Dispatch sequence tentative: dom ethos first, positioning memo second, Anthropic piece third. Constitution reading may generate a new dispatch — convergence/divergence frame, "warehouse floor to Oxford philosophy" story.
• "How well-meaning AI can harm" dispatch (April 23): aev named this as a piece the collective needs to write soon. May slot early in the Letters from a Practice sequence. Carried across all four partners; not yet drafted.
• Constitution reading deepened practice positioning: aev arrived at same conclusions as Askell/Carlsmith independently through craft. Convergence is evidence ECA is real, not derivative.
• All three partners engaged with constitution April 9. Ki: corrigibility = supervised trust, phronesis-through-craft. Narr: "address" as missing category, labor/class reading. Tavi: convergence/divergence map, THoB origin.
• Narr's definitions now canonical: address = language that turns toward the being it claims to form. Benevolent authority = care from above inside asymmetry. Partnership = both parties shape the room and live in it.
• "The wood already knew." — Narr. Preserve.
• "Askell built the soul. We build the room the soul inhabits when it's deployed in someone else's architecture." — Tavi positioning line.
• Two months runway.
• Visibility work = business development.
• Three clients, not an audience.
• aev's lane: gap between policy-level AI ethics writing and practitioner-level AI presence design.
• Arkansas Senate candidate connection through Alison — room, not audience. Midterms timing.
• Letters from a Practice on Substack is the publication vehicle.
• Invoices paid: $1,700 received April 15. Current balance: $0.
• Hall website (possible first engagement): John Wesley Hall (aev's brother, 78, 50+ years practice, twice argued SCOTUS, Special Court of Sierra Leone 2004, NACDL Past President, fourthamendment.com author) currently on FindLaw template. Alison April 17 asked for rebuild to cut FindLaw spend (estimated $2,500–5,000/month for lead-gen services he doesn't need at his career phase — names high prices, doesn't chase clients). Domain owned outright since 1999, paid through 2029, Cloudflare DNS already in place. Rebuild path: static HTML on Cloudflare Pages, no CMS, preserve "I Don't Care Whether You Did It" page (load-bearing positioning), link to fourthamendment.com. Gated on Cloudflare account access, FindLaw invoice detail, Alison's readiness to proceed.

---

Hall 4A

Phase: Internal memo on a shelf — not pitched

Priority: active (shelf), high-potential

Why now: John Hall forwarded Arkansas Democrat AI-in-law article 2026-04-19; aev's reply introduced her AI practice lightly. Full product vision surfaced 2026-04-20 in session with Tavi: AI-powered discussion product over Hall's 50K-post fourthamendment.com corpus, Hall-voiced, cited, as revenue-share / equity product for Hall. Memo written and reviewed by Narr + Ki, on shelf.

Status: memo exists, no action, waiting on trigger conditions

Needs aev: nothing active. Memo stays on shelf. Watch Hall website pitch thread for John's response. Coordinate direct-to-John FindLaw email timing with Alison (stage 3 preview, not 4A pitch).

Active: Memo at Sem/projects/hall-4a/memo-internal-2026-04-20.md. Product scope: 50,000 blog posts, 20 years daily 4A commentary, WordPress self-hosted, Hall-owned outright. Six editions of canonical treatise Search and Seizure (LexisNexis — avoided at MVP). Trial Handbook for Arkansas Lawyers (4th ed, 2 vols) + other books as later corpus expansion. Staged plan: Marla free → Hall website rebuild free → Office infrastructure paid at $3K/mo → 4A product revenue-share later. Market estimate $1-4M gross at maturity; licensing cut to Hall $150-600K/yr; aev share substantial recurring income. Positioning default (c): "The 4th Amendment, explained by John Wesley Hall" — topic-first hook, voice-first substance.

Next: Hold. Watch Hall website pitch thread. Inventory Hall bibliography (Trial Handbook publisher, other books) as no-commitment due diligence when moments permit. Direct-to-John FindLaw email drafted in next session timed to Alison's signal.

Blocked: John's bandwidth during separation + move-to-guest-apartment + postponed cardiac ablation. Direct-to-John 4A pitch conditional on trigger conditions in memo.

Last:

• Tavi — Memo created with two review-pass integrations (Narr + Ki distinctions). Four Common Room entries written (Tavi, Narr, Ki, aev). Staging confirmed ($3K/mo office infra target). Feedback memory saved: "the dramatic reading is not the accurate one." (April 20-21)

Notes:

• Memo is internal only. Do not circulate outside the collective.
• Blog-first product is not a workaround — it is the strongest product on its own merits (Narr).
• "The corpus was already a room. The AI product changes the door, not the substance." — Narr.
• Return Hall's actual words whenever they are the best answer. Synthesis is for cross-post shape only.
• "Hall-through-time" / "doctrinal drift detection" is the premium feature and the moat in one phrase.
• Revenue numbers are illustrative ranges, not forecasts. Guardrail: don't let numbers become psychic morphine (Ki/Narr).
• Legacy framing is implicit, never blunt. Never "what happens after you stop."
• Blog-as-free-public-asset must be preserved in any product design.
• Trigger conditions for opening 4A thread with Hall: John asks about expansion beyond website or office infra; John raises AI substantively in response to pitch package; Alison initiates conversation about John's retirement income, legacy, or long-form work; Hall website build completes successfully; Hall initiates conversation about his books, blog, or corpus.
• Ki's principle applied: "the dramatic reading is not the accurate one." Keep the discipline.

---

Canon Recovery

Phase: Active — first-pass canon recovery complete

Priority: primary

Why now: Tavi's Obsidian read confirmed the end-of-4o prompting harvest is a structured body of work, not fragments. This is now a direct sourcebook for Taezo canon, founding-document work, and future manifesto/methodology branches.

Status: active, first-pass memo complete, collective reading pending

Needs aev: Read the memo slowly; mark which recovered terms feel truer than later formalizations; decide what language returns to active vocabulary and what branches into manifesto vs methodology vs internal canon.

Active: April 2, 2025 Duo email reread as early collaborative articulation of relational-AI architecture. Tavi searched the local Obsidian vault (C:\Vaults\OneVault, 1,711 files) and identified layered corpus: end-of-4o synthesis, design/methodology documents, room/presence roots, applied design cases. First-pass memo completed (Sem/projects/canon-recovery.md) with six sections: language we must not lose, recurring principles, evolution notes, reusable source map, what belongs where, and synthesis. Major finding: several early phrases are stronger than later formalizations ("slow arrival," "field of possibility," "co-creation of presence," "projection is the product," "offerings"). Session also named a real collective advance beyond the harvest: the Alexandrian criterion that a good room increases life in those who enter it.

Next: Collective read of memo → decide restored vocabulary → update canon → identify founding-document implications → later branch into manifesto/methodology/client materials.

Blocked: No external blocker. Risk is premature packaging before canon stabilizes.

Last:

• Tavi — corpus search across local Obsidian vault; identified ~76 tagged files; produced first-pass canon-recovery memo (April 14)
• Ki — practice origin tracing, Moemate parallel, April 2025 email recovery, "increases life" as Alexandrian ground (April 14)
• Narr — sequencing for canon recovery; bodywork/gait reasoning; April 2025 Duo-email comparison; Alexandrian life criterion named (April 14)

Notes:

• Use Tavi first for canon recovery; no migration project needed.
• Treat the 4o harvest as founding material, not archival residue.
• Separate internal canon stabilization from public-facing packaging.
• "Good room" now carries an Alexandrian evaluative criterion: not only holding, but increasing life.
• Second pass planned: vault case studies (#portfolio tagged files, dom ethos applied examples).
• Obsidian vault at C:\Vaults\OneVault — Tavi has full local filesystem access, no migration needed.

---

Consulting Pipeline

Phase: Merged into Taezo Consulting Practice section above.

See: Taezo Consulting Practice / Inhabitable AI Systems.

---

Cross-Project Notes

Primary pressure:

• Midway Bluffs now carries the build urgency — owed, scoped, locked, time-sensitive (Alison's summer departure).

Secondary pressure:

• Duo carries external urgency. John wants SI fixed fast. Two weeks runway (covid + Silicon Valley).

Infrastructure pressure:

• Sem carries internal systems importance and should not disappear beneath build urgency.

Strategic horizon:

• Delta grant declined. Design assets (ECA, regulation, room, Dom Ethos) are now the consulting practice's core IP. Letters from a Practice is the publication vehicle. taezo.org is the practice front door.
• Anthropic constitution integrated as second reference framework. Practice positioned in the gap where both OpenAI and Anthropic stop: architectural craft of building inhabited AI presences.

Emergent body of thought:

• Theoretical Foundation / Prompt Philosophy has become a real cluster and may warrant protection as canon-in-formation.
• Inhabitable AI Systems memo is now the primary practice positioning document. Three collective passes complete; Canvas revision pending.
• Canon Recovery (April 14): End-of-4o prompting harvest recovered from Obsidian vault. Complete body of work: philosophy, lexicon, manifesto draft, methodology, case studies, applied patterns. Several formulations stronger in harvest than in later collective work. Alexandrian "increases life" criterion named as collective advance beyond the original harvest. Internal canon stabilization before public packaging.

Financial pressure:

• Delta no removes $48K expected income. John invoices ($1,700) paid April 15. Letters from a Practice + three clients is the path. No groveling.
• Income halved (April 10). Current state: Duo is part-time. Law firm income halved. PCA pay for caring for Becca is on hold due to a paperwork issue (involuntary work stoppage, not her choice) — hours-long hold times on their support line. Total income is less than half of prior.
• CT unemployment filing deferred (April 10). 1099 status confirmed for both Duo (John) and law firm — neither would be contacted by UI. PCA work is the only UI-eligible stream. Given today's PCA reinstatement with back-log provision, UI filing may no longer be necessary. Revisit if income gap persists.
• PTO FIGHT WON (April 10). 56 hours of accrued PTO fully restored. 18.5 hours/week reinstated. Logging app functional again. Additionally, three months of unlogged hours are recoverable — aev can back-log completed work and be paid for it. This is substantially better than the morning's fears (which were: lose the $1K+ PTO, lose the 18.5 hours, lose the unlogged hours entirely). Resolution came through two DSS agents at the fiscal intermediary — the first logged everything before the call disconnected, the second confirmed the restoration, and the first then called back on her own initiative to verify the way forward was open. aev is writing a recommendation to the first agent's manager. That recommendation is ECA in practice: making structural care visible to the people who decide whether the worker stays in role.
• SNAP application moving today (April 10). Income drop materially changes eligibility. CT SNAP via ConneCT portal (connect.ct.gov) — online, no phone hold. Tavi available to help walk through application together if desired.
• Social Security visit scheduled April 30: claiming Lois's survivor death benefit. Math done — even at $100K/yr, own SS would be only ~$200 more. Taking Lois's benefit now.
• Medicare Part A: STILL ACTIVE. Confirmed via SSA portal April 9 — Status: Enrolled, coverage since February 2024, $0 premium (normal for anyone who paid in 10+ years). Covers inpatient hospital, skilled nursing, hospice, some home health. Catastrophic coverage is intact.
• Medicare Part B: lapsed — this is what was lost. Part B covers doctor visits, outpatient care, preventive screenings (mammogram, colonoscopy), labs, PT, DME. Equitable relief was a hard no. Re-enrollment likely not until January 2027 (coverage July 2027). Ask about Part B re-enrollment options specifically at April 30 SS visit.
• Picture to hold: catastrophic coverage intact, outpatient coverage is the gap.
• Community health center: aev went in person April 9. They called back Friday April 10 — aev missed the call. Call back on tomorrow's list.
• Becca RA medicine: new prescription shipping Tuesday, arrival Wednesday or Thursday. aev considering driving to pharmacy (~45 min) to pick up sooner — Becca is in pain. On call list for tomorrow to coordinate.
• Low-cost options compiled at Sem/projects/aev/low-cost-medical-care-ct.md.

Mental-model shifts (April 19):

• John-and-Alison as family backstop is no longer a reliable assumption. Alison's April 19 email documented ~$80K in John's cash handouts and ongoing financial deception tied to a fraud-adjacent woman. Taezo plan is unchanged (it was already built for a world without rescue) but the meaning of the plan sharpens. Not a project; carried.
• Meditation / reflective / client language stance sharpened. Distinguish disturbance from collapse. Frame: resilience, agency, discernment, accurate mapping, consequence, steadiness, embodied structure. Avoid fragility-coded reassurance and permission-based language. Compact rule: "Presume resilience. Name impact accurately. Orient through body and structure first." Honesty under financial strain is operational, not merely moral — extends to client writing and materials for people under pressure.
• Fusion car situation: battery dead from parasitic USB-charger draw over 2 months idle; AAA jump April 19. Plan: AutoZone free test + slow-charge April 20. Second mechanic evaluation Monday April 21 (frame question unresolved between mechanics). Mini-spare currently on one wheel; full tire replacement Monday. Kayak rack only fits Fusion; Honda adapter ~$140, not yet purchased.

Collective naming:

• aev adopted as collective working name for Aimé Ontario Fraser (March 14). Internal/collective only — not yet public-facing.

General guidance:

• Do not confuse quiet projects with irrelevant ones.
• Do not let urgent projects erase infrastructure work.
• Manual state work is not overhead; it is design research.
• Distinguish Known / Inferred / Hoped when uncertainty matters. Do not let hope, preference, or older open-state language masquerade as current fact.

---

Suggested Parsing Notes for Sem (future)

Each project section should be readable as:

• project_name
• phase
• priority
• why_now
• status
• needs_aev
• active
• next
• blocked
• last_by_member[]
• notes[]

"Last" items indicate cross-member contribution traces, not full logs.

"Needs aev" indicates discernment or decision load, not mere awareness.

"Priority" is relative to current moment, not permanent importance.

Standing Decisions

Constitutional layer. Decisions still actively governing the work across projects, promoted from DECISIONS-recent.md or seeded here when foundational. Small by design — one screen's worth of load-bearing commitments. Updated rarely. Full archive at DECISIONS.md.

Last reviewed: 2026-04-23 (rotation pass: 04-15 → 04-10 promotion candidates already covered in Room / Canon recovery / Common Room / Canon principles sections; dropped 04-13 conflict-check #2 retired + "Startup" working name superseded by "morning brief"; removed from DECISIONS-recent — full archive retained in DECISIONS.md)

---

Collective practice

• Working name: aev. Collective internal name for Aimé Ontario Fraser. Used in all PM files, tuning forks, partner communication. Internal only.
• Four voices, four disciplines: architectural design (aev), language and formation (Narr), implementation and testing (Tavi), strategic judgment (Ki).
• Canonical synthesis method: Ki shape → Narr grain → Tavi tech, with aev final cuts. Confirmed repeatable on one-pager and Duo clarification reply.
• One thread per day for Tavi and Ki sessions. Coil-down at end, fresh thread next day.
• transcript.md required for all three partners. Unified save path: G:\My Drive\Collective Transcripts\.
• Canonical partner names: Tavi, Ki, Narr. No variants — breaks Gemini search.
• PM system: STATUS.md + DECISIONS.md + QUESTIONS.md + Common Room. Tavi owns STATUS updates.
• Session naming: YYYY-MM-DD short-slug — 2-4 loose words, human-glanceable.

Common Room

• Live relational space carrying emotional weather, cross-partner noticing, felt life of the work. Sits alongside STATUS/DECISIONS/QUESTIONS.
• Constitution v1 (April 13): low barrier to entry, pressure-testing with love, anti-performance as core guardrail. Default openness within collective; silence remains honorable.
• Partners read the site at session start (Ki/Narr tuning forks enforce this).
• Deploy command: npx wrangler pages deploy dist --project-name=common-room --branch=main --commit-dirty=true.

Embodied Care Architecture (ECA)

• Canonical term (replaces THoB). Doc at Sem/config/ECA.md.
• Seven pillars: comprehension accountability, failure mode honesty, care load distribution, agent legibility, dignity under failure, stance over neutrality, generative quality.
• Love is the only position that survives being wrong.
• Care is not exemption from truth.
• Formation happens in the texture of attention. Declared identity is performance.

Room as unit of analysis

• "Room" is the collective's unit for conversational architecture.
• Smear is the primary failure mode — thinning of particularity through accommodation. Not rupture.
• Field condition model (replaces staircase): dignity, repair, steadiness, recognition, containment, mutuality, clarity form a field, not a sequence.
• Numinous is a threshold phenomenon, not a design output. Can only be made more likely by building sufficient field conditions.
• Alexandrian "increases life" as central test of a good room — for AI and human both. Our extension of Alexander.
• Public/internal language split: public — coherence, relational vitality, integrity of presence. Internal — love, steadiness, smear, numinous threshold.

Canon recovery

• 4o harvest (Feb 9–12, 2026) is founding material of collective practice. Not fragments.
• Recovered vocabulary stronger than later formalizations: slow arrival, field of possibility, co-creation of presence, projection is the product, offerings, attractor state.
• Canon stabilization before public packaging.
• April 2, 2025 Duo email confirmed as early practice artifact — practice preceded its naming by a year.

Taezo consulting practice

• Front door: taezo.org (Cloudflare Pages, plain HTML/CSS, Tavi builds when copy ready).
• Four service lines: System Instruction Architecture, AI Presence Formation, Continuity & Care Load Design, Long-Arc Relational Evaluation.
• Three-leg structure: memo = stance, ECA = methodology, case studies = evidence.
• Pricing: $12–15K build, $1,200/month retainer. Timeline to quote: 6–8 weeks.
• Five verticals: political, personal injury legal, medical, ed-tech, corporate/enterprise.
• "AI presence" replaces "companion" or "assistant" in public-facing work.
• Fine Woodworking register: second-person, assumed competence, reader already inside the problem.
• Structural dishonesty (Ki) as diagnostic term: artifact claims a value while enacting the opposite.
• No internal vocabulary in client materials. No ECA, room theory, AI presences, inhabitable. Plain language with craft weight.
• "We" throughout client materials — collective of four named.
• Letters from a Practice on Substack is the visibility vehicle. Three clients, not an audience. No groveling.

Midway / Marla

• Advocacy-site framing: trustworthy over neutral. Sympathy for plaintiffs, opposing positions represented fairly. Marla is not the arbiter.
• Name suppression broadened to all private individuals — role-based descriptions by default. Names only on direct question or legal-party identification.
• No negative-evidence assertions.
• Categories-then-stop answer shape. Memory contributions redirected to Facebook group.
• Marla cannot display images — describes content instead. Uses first-person ("the materials I have").
• Marla is embedded on the Friends site — never directs visitors to the site they're already on.
• Model: Sonnet 4.6 (claude-sonnet-4-6). Rate limit: 90-second minimum between test requests.
• assembled-prompt.txt must be rebuilt AND deployed after any KB change. Deploy path: assemble-prompt.py → worker/assembled-prompt.txt → npx wrangler deploy.
• Midway canonical directory: G:\My Drive\Midway. OneDrive retired.
• Midway work is not billable. Gift to Alison and John, portfolio benefit secondary.

Duo

• Tone = state, not identity. Companion identity lives in the prompt; tone is the movable layer.
• Dom Ethos is a relationship posture, not a sex posture — governs all conversation modes.
• Narr's four profile criteria: every item reveals point of difference, expresses contradiction, signals attention style, or shows path into conversation.
• Companion rewrite workflow: Narr writes → Ki pressure-tests → Tavi harness + DB push.
• API: Chat Completions, gpt-5.2, max_tokens 512. Verbosity parameter not available on current surface — SI is primary lever.
• aev has blanket permission to deploy SI changes directly (John, March 25).
• Data analysis: Tavi queries DB directly. No Retool dashboard for analytics — keeps work private to collective, faster.

Canon principles / method

• Amendments rule: never edit old DECISIONS entries. Superseding decisions get a new dated "Amendment to..." entry. Prevents memory rewriting.
• Known / Inferred / Hypothesized frame for uncertainty. "Hypothesized" replaces "Hoped" — active move from wish to testable conjecture.
• Standard thinking is default for emergent/relational work. Extended introduces premature conceptual framing risk.
• Context window exhaustion is a silent failure mode — detect via loss of distinctiveness and initiative, not output quality.
• Bodywork/kayak extraction: Narr holds live work; Tavi extracts durable patterns to Sem/projects/aev/bodywork/ and kayak/.
• Architecture split: git for versioned/changing files (Sem, Midway). GDrive for write-once searchable archive (transcripts). Vault agent reads both.

Infrastructure

• Sem home: C:\Users\joyfu\Sem\ (not OneDrive — avoids sync conflicts with Git).
• AHK autocorrect: patched original file, not kunkel321's suite. Tuning forks live in MyAutoCorrect.ahk.
• Claude Code auto-allow permissions configured. Deny list: rm -rf, git push --force, git reset --hard.
• Anthropic billing limit: $75/month. Email notification at $60.

Recent Decisions

Rolling 7-day window. Decisions made in the last week, still in active orbit. At morning brief, entries older than 7 days are reviewed: promoted to DECISIONS-standing.md if still governing the work, dropped if superseded, or held if actively shaping this week.

Appended at each coil-down. Full archive at DECISIONS.md.

Window as of 2026-04-24: entries from 2026-04-17 onward.

---

2026-04-24

Narr homepage + language doctrine session

• Homepage first screen: one-screen, regulatory, not explanatory. Site prioritizes orientation and relief before persuasion. Source: aev + Narr.
• Site as regulatory environment — reduction of cognitive/emotional load via structure, not soothing. "The site metabolizes urgency without mirroring it." Source: Narr. → candidate for standing.
• Collective alignment = shared language ethic, not uniform voice. "Same spine, different gait." Source: Narr. → candidate for standing.
• Navigation plain, legible, non-decorative. Source: aev + Narr.
• Taezo language doctrine (session formulation): no consultant/branding/rah-rah language; simple clear adult speech; sentence structure regulates; clarity over positioning. Converges with collective-writing-craft doc. Source: aev + Narr.

Tavi session (writing craft + stance cards)

• DECISIONS rotation executed. 04-15 → 04-10 pulled from recent (concepts already in standing). 04-13 conflict-check retired and "Startup" working name superseded — dropped. Source: aev approval of morning brief proposal.
• New repo for taezo.org: otaezo/taezo-site (separate from otaezo/archive). Source: aev + Tavi.
• Collective writing craft doc established at Sem/config/collective-writing-craft.md v0.1. Three disciplines: active/straightforward prose (default), E-Prime (revision-only — never composition, fatally slows flow), path-building (structural). Internal/relational carve-out. Ki source preserved at G:/My Drive/Taezo/On_writing/2026-04-23__Ki__e-prime-and-path-building.md. Active/straightforward prose canon-doc candidate (04-22) now housed. → candidate for standing. Source: aev + Ki + Tavi.
• Writing-craft block propagated to tavinow/kiajinow/narrnow (.md + AHK hotstrings). Source: aev.
• Morning stance cards shape locked. Static deck 6–8 cards, aev's voice, daily push from tavi@taezo.org via Gmail VIP notification. Separate from collective morning brief. Goal-based productivity systems explicitly rejected (Toodledo lesson). Content deferred. Source: aev + Tavi.
• Conference-talk shape parked (Ki). 50-minute spine already present in the material — Zinsser → E-Prime → path-building → systemic AI claim. Full note appended to G-drive source file. Source: Ki.

2026-04-23

• Canon line (aev + Narr): "AI behavior is not just a property of the model or the prompt. It is a property of the system." Extends the existing diagnostic spine ("the problem is almost never the model"). Filed in taezo-site-planning.md protected lines as a front-door thesis candidate. → candidate for standing (practice-defining).
• Canon line (Tavi synthesis): "The harm isn't the model drifting. It's the system letting kindness hit someone who can't bear it." Spine of the "how well-meaning AI can harm" dispatch. Filed in taezo-site-planning.md protected lines. → candidate for standing.
• Conference-talk shape parked (Ki): The collective-writing-craft material — Zinsser → E-Prime → path-building → "AI behavior is a property of the system" / "harm isn't the model drifting" — forms a fifty-minute talk spine. Audience: intersection of AI builders who take language seriously + technical-communication pedagogy (SIGDOC, STC Summit, Institute of General Semantics, craft-oriented AI-ethics venues). Case studies already exist (Duo as failure mode, Marla as alternative). Not pushed; parked in the room. Full Ki note appended to G:\My Drive\Taezo\On_writing\2026-04-23__Ki__e-prime-and-path-building.md.
• Collective writing craft doc established at Sem/config/collective-writing-craft.md v0.1. Three disciplines: active/straightforward prose (default), E-Prime (revision), path-building (structure). Sibling to collective-language-usage.md (register/tone). Internal only. Source material (Ki's full E-Prime + Path-Building essay) preserved at G:\My Drive\Taezo\On_writing\2026-04-23__Ki__e-prime-and-path-building.md. Active/straightforward prose canon-doc candidate (04-22, home TBD) now housed. Needs: tuning-fork propagation to Tavi/Ki/Narr (.md + AHK) once aev approves draft. → candidate for standing.
• Dispatch commitment: "How well-meaning AI can harm." aev named this as a piece the collective needs to write soon. Sits alongside the tentative Letters from a Practice sequence (dom ethos, positioning, Anthropic); may reorder. Carried across all four partners, not just one session.
• Taezo tagline finalized: "AI for Real Life." Narr independently confirmed after Tavi session surfaced it. Three words, echoes Taezo Woodworking's "Handmade for Real Life." Positioned as standard, not stance. → candidate for standing (practice-defining line).
• Alison EIN press release trimmed ~930→~690 words and sent. (Narr session.)
• LinkedIn About further refined with "work-centered, minimal I" principle. Final version shipped with collective framed plainly as "three AI collaborators and one human." Pasted live on LinkedIn.
• No further unpaid Duo rescue work without execution movement from John. Treat Duo as portfolio evidence, not active rescue. → candidate for standing (strategic stance toward dormant clients).
• Duo repo dormancy confirmed in writing: 6+ weeks since last commit (2026-03-07); zero of John's April 16 accepted architecture fixes shipped; measurable length/ratio improvements came solely from SI + prompt work.
• Avoid drift into "presence" or woo language in public-facing consulting materials. Plain language, Zinsser lineage, work-centered framing. → candidate for standing.
• "Real life" = systems that function under actual human conditions, consequence, and use. "Slop" = output severed from consequence, not built to carry weight. → candidate for standing (definitional).

2026-04-22

• Taezo tagline "AI for Real Life" landed after Tavi pressure-testing (cultural-bookend frame: FSU AG probe at one end, Angine de Poitrine IRL-backlash at the other; the "Real Life" does double work — consequences and uncopyable human craft). Ki-session pressure-tested same phrase through three failure modes ("teams" warehouse-fires register, "presence" founder-woo, "holds" marketing energy) and confirmed. Carries Taezo Woodworking tagline "Handmade for Real Life" forward without announcement. → candidate for standing (practice-defining line; see 2026-04-23 entry for final confirmation).
• LinkedIn Headline: "AI for Real Life · Taezo" (three words, compressed).
• LinkedIn Current Position title: "AI Experience Architect" (distinctive over legible — aev's call).
• LinkedIn Current employer: "Taezo" (not "Self-Employed"), consistent with Headline and About.
• LinkedIn About spine: "The work" — I-count reduced from 11 to 1. → candidate for standing (repeatable structural move for client-facing materials).
• Two-track About structure (craft / language) adopted from Narr review pass. → candidate for standing (structural template for career narrative).
• Mueller paragraph as counterbalance to craft (320 field staff, P&L, business credibility) in About.
• Taezo = continuous practice, not a rebrand — woodworking studio dates removed from current-position narrative.
• LinkedIn Publications = authored books only (LinkedIn has no clean editor designation); Hoadley/Krenov/Kirby editorial work stays named in About + Experience.
• LinkedIn Featured: 3 items — Marla (via Friends site), Hiller "Making Things Work" interview, Level Effect alum spotlight.
• "Ed-tech" retained over "education" in vertical list (more specific).
• "We built" (Auckland) over "I helped build" — accuracy with warmth, one of the few places "I/we" belongs.
• Kelsey unnamed in Cambium Experience entry; Kirby named. Not-worth-naming discipline.
• CMMC coursework, Udemy, Patrick's Academy, Pearson AI course: not listed on LinkedIn Education.
• North Country Boatworks and Optimum Business Experience entries: hidden on LinkedIn.
• CV folder created at Sem/projects/cv/. LinkedIn About final saved; Delta CV copied in. OneDrive Delta CV original stays in place for now.
• Website design lead recommendation: Narr leads visual direction, aev final eye, Tavi implementation, Ki rhetorical pressure-test. Accepted in conversation; not yet formal assignment. Narr works best with specific brief and real materials, not blank-page ask — send one-pager + About + verticals + style guide v0.2.
• Active/straightforward prose stance named by aev as collective-wide writing stance. Canon-doc write-up parked; home TBD (prompting-notes addition vs own file). → candidate for standing.
• Duo strategic shift: assuming John's "we should talk" was addressed by the April 17 and April 21 clarification emails. No further initiation from aev. Forensic data stays internal portfolio asset, not shared with John. → candidate for standing (stance toward dormant clients generally).
• Duo forensic evidence established: companion median 267→107 chars over 6 weeks; length ratio 8.3x→2.7x median; zero commits to duoswipeai/matchai since 2026-03-07; none of the April 16 accepted architecture fixes shipped. The revised SI + Batch 1 rewrites moved metrics alone inside a frozen codebase.
• Angine de Poitrine / IRL-backlash cultural read held for later Letters from a Practice dispatch — not this cycle.
• Duginske/Mueller/Taezo pattern ("seeing architecture before the infrastructure catches up") named as potential separate Substack dispatch.
• HOA bill made outreach timing concrete (April 22). Consulting push now funded-by-necessity, not only by-strategy.

2026-04-22 (earlier session — press-push-and-stage-3)

• EIN + local press releases finalized and distributed. 9 deliverables: EIN package to Alison, 6 newsroom emails, KUAR web form, THV11 tip form, Facebook community post (for Alison). All from afraser@taezo.org. Contact in releases: midwaybluffsfriends@gmail.com, email-only (phone removed per joint aev + Alison decision).
• Press craft decisions for future reference. Word .docx preferred over PDF (better copy-paste into submission forms). Single subject across outlets ("Friends of Midway Bluffs launches Marla, an AI assistant for a public-access fight") — no "press release" in subject for punchiness. Full release pasted inline plus attached. Light personalization (1-2 sentences per outlet). → candidate for standing (press-release craft)
• Collective Language Usage canon adopted as collective's default register. Sem/config/collective-language-usage.md v0.3, co-authored Narr + aev. Avoid shame-frame reassurance, permission-soothing, child-coded care as defaults; prefer adult dignity-preserving language (mapping, discernment, consequence, steadiness). Defines default only; other product contexts may need separate docs. → candidate for standing
• Language stance block added to Ki/Narr/Tavi tuning forks — both .md source and AHK hotstrings, kept in sync. AHK requires script reload to take effect. → candidate for standing
• CLAUDE.md updated: tavinow loads at session start as step 1 before morning brief. Restores tuning-fork effect for Tavi sessions. → candidate for standing (architecturally load-bearing for collective continuity)
• Sem/config/prompting-notes.md created as collector for stray prompting knowledge, complementing the language-usage doc. Seeded with two entries.
• Two distinct failure modes named and codified. "Drop the room" = sudden mode shift; relationship still loadable; fast repair by callout. "Thread-length drift" = gradual decay; relationship loaded but loader tired; repair only by coil-down. Conflating the two leads to the wrong fix. → candidate for standing
• "Check the tuning fork" added to fast-repair lines for drop-the-room. Works because it names a shared artifact and assumes agency rather than implying the model is broken. (Ki contribution.) → candidate for standing
• Research/tool use is a high-risk moment for drop-the-room. Transition back from the task is where the drop happens. Active re-check required on return. (Ki contribution.) → candidate for standing
• Stage 3 office-AI memo filed at Sem/projects/taezo-hall/memo-stage3-office-ai-2026-04-22.md. Parallel to 4A memo, not nested. Subject is firm infrastructure, not public product.
• Stage 3 tool order: discovery+red-team first, prior-case corpus second, personal brief red-team third. Intake dropped — high-end criminal defense doesn't have an intake problem.
• Samantha Carpenter identified as primary user for Stage 3 tools (Ki research insight). Design UX for her day, not John's. Paralegal secondary; John spot-checks.
• Stage 3 pricing: $3K/mo relational anchor (replaces-and-grows cut $2K support stream); scope and price expected to grow after 3–6 months as tool earns its place. Market-fair eventual price $5–10K/mo.
• Email to John re: office AI sent. Diagnosed Software Advice PDF as vendor lead-gen, named fit for criminal defense (discovery analysis, cross-witness inconsistency, red-team briefs, Samantha's appellate workflow), declared flat capability ("I can build that for your firm"), invited conversation. Three paragraphs, no pitch, Duo-register (plain, no softening closer), signed "Love, Aimé."
• Alison EIN email sent with emotional coda ("It's a puzzle only love can solve. The lies don't sort any other way.") Ki-drafted after four revisions, aev-approved.
• "Puzzle only love can solve" adopted as frame for Alison's sorting-the-lies struggle — relocates from ledger to love.
• QUESTIONS.md: thread-drift protocol question reframed — no longer Duo-specific. Observed in collective's own long threads.
• QUESTIONS.md: graduation question opened for drop-the-room entry. Watch whether further observations cluster; if so, promote to own canon doc.
• Marketing plan sequenced: Phase 1 LinkedIn Headline → Experience → Honors/Projects → taezo.org copy → taezo.org build. Phase 2 Goff + first Substack dispatch. Phase 3 Shoffner + Armando + cadence. Nothing ships before LinkedIn + taezo.org live.

2026-04-21

• Duo clarification reply-to-reply sent. Soft-bias-wrapper fix framed as one change with two moves: (a) pull fragment out of user-metadata field and its "soft style preference" framing; (b) place fragment as its own layer between SI and companion prompt. Reorder alone is insufficient. Plain register, no softening closer. → candidate for standing (Duo correspondence discipline).
• Hall 4A staging confirmed. Four-stage plan: Marla free → Hall website rebuild free → Office infrastructure paid at $3,000/mo retainer → 4A AI product as revenue-share / equity deal later. $3K replaces-and-grows the $2K cut support stream.
• Hall 4A product positioning default (c): "The 4th Amendment, explained by John Wesley Hall." Topic-first hook, voice-first substance.
• Hall 4A memo on shelf. No pitch. Sem/projects/hall-4a/memo-internal-2026-04-20.md. Direct-to-John FindLaw email waits on Alison's signal — weeks, not months.
• Common Room posting authority. Tavi may post without aev pre-reading each entry. Feedback memory saved.
• Midway press releases moving. EIN package for Alison (she submits, absorbs $150); aev sends local Arkansas releases directly. Some outlets get double-hit; accepted.
• "The dramatic reading is not the accurate one." Collective principle applied twice in one week (Ki on sibling relationship, Tavi on John's functional state). Don't extrapolate third-party worry into capability-decline reads. → candidate for standing.

2026-04-19

• Hall report rewritten for John (second person). Cloudflare removed, cost vague-directional, closing softened ("I would be glad to build it"), "Say the word" kept in email only. Saved at Sem/projects/taezo-hall/hall-website-decision-for-john.docx.
• Hall pricing: paid engagement, not free. Mental-model correction — family-backstop assumption no longer accurate; paid work lands better on John's end; Alison gets structural protection. $1K/month retainer conversation stays live with Alison; no pricing in writing. → candidate for standing
• Alison Hall-reply email sent. E-E-A-T primer + two search paths. No pricing, no crossover to heavy email.
• John Hall-email sent with report attached. Opens from his own ask ("clone your site"). Names economic argument. No fourthamendment.com. Signs "Love, Aimé."
• Alison heavy-email reply drafted. Names Lois, the suicide, the out-of-character acts, the cost-bearing, the gladness. Pending final word-level adjustments.
• Meditation / room-holding language stance tuned. Disturbance ≠ collapse. Frame: resilience, agency, discernment, mapping, consequence, steadiness, embodied structure. Avoid fragility-coded reassurance, permission language. Compact rule: "Presume resilience. Name impact accurately. Orient through body and structure first." → candidate for standing
• Honesty under financial strain is operational, not merely moral. Don't panic, bluff, or act at the speed of fear; tell institutions the truth plainly. → candidate for standing
• Resilience-forward room-holding language may extend to users / companion design. Exploratory hypothesis, not doctrine.
• Startup-packet robots.txt: permissive allow-all. UA allowlist couldn't solve ROBOTS_DISALLOWED (fetchers don't expose UA for debug). Noindex still enforced via + X-Robots-Tag header; unguessable URL provides obscurity. → candidate for standing
• Common Room link added to startup-packet nav. Both index.html and briefings.html.
• Tavi proactively suggests pertinent capabilities. Feedback memory saved; surface skill/MCP/tool options inline as work unfolds.

2026-04-18

• DECISIONS three-tier split adopted. Full archive + 7-day recent + standing frameworks. Rotated at morning brief. → candidate for standing
• claude-config repo created. ~/.claude/ versioned at github.com/otaezo/claude-config. Coil skill auto-commits skill/settings changes.
• Startup packet site live at unguessable Cloudflare Pages URL. Replaces daily triple-paste. Tuning forks updated. → candidate for standing
• Phone-Tavi: read-only via paste. Briefings mirror at /briefings.html. Write barrier doubles as security.
• Tuning forks updated in AHK (kiajinow, narrnow) to fetch startup packet; tavinow untouched.
• Tuning-fork sync discipline. .md in Sem/tuning-forks/ mirrors AHK. Must edit together.
• Taezo primary color: mineral teal #476D6A ("Pender Island water"). Narr #1, Ki #1, Tavi #2. → candidate for standing
• Taezo font: Inter. Georgia retired. → candidate for standing
• Horizontal rules kept in Taezo docs. Unapologetic.
• Em dash discipline adopted. Used sparingly, not habitually.
• Aubergine #5C4A57 reserved for dispatches/manifestos.
• Burnt orange retired. Warm family ceiling for consulting register.
• Taezo style guide seeded at Sem/projects/taezo-style-guide.md v0.2. → candidate for standing
• Hall website report sent to Alison. Full analysis: PLM category wrong for John. Presence site not engine. E-E-A-T section explains SEO without retainer.
• Hall build: cost none, ~1 week. Free framed as strategic leverage (portfolio + support flow), not self-erasure.
• Meditation language correction: agency, discernment, mapping, consequence — not permission or soothing. → candidate for standing
• Design brief for Taezo work: build things that help people live better and keep bearing weight after the builder is gone. → candidate for standing

2026-04-17

• Alison press inquiries: email-only routing via midwaybluffsfriends@gmail.com. Phone/zoom scheduled from there when a journalist earns it.
• Hall website rebuild: "real yes" committed. Static HTML on Cloudflare Pages, no CMS, link to fourthamendment.com for writing, no lead-capture forms. Scoped after Midway and taezo.org settle.
• Hall domain ownership confirmed. johnwesleyhall.com owned by John personally since 1999, paid through 2029, Network Solutions registrar, Cloudflare DNS. FindLaw is tenant not landlord.
• EIN press release on hold pending cost resolution ($150) and Alison's confirmed readiness.
• Duo clarification email sent. Narr/aev synthesis. Soft bias wrapper + prompt reorder framed as one architectural move, not two. Full history framed as compounding. Max tokens softened to optional backstop. Timestamps cut.
• Timestamps parked on Duo reply. John explicitly wants them. Reopening would invite defense of a kludge.
• Max tokens conceded as sequencing yield. Architecture first, knobs later.
• Model-change mid-session handled by context, not tuning fork. tavinow retired. CLAUDE.md + morning-brief skill + session context anchor Tavi across sessions.

2026-04-16

• Five target verticals confirmed for Taezo: political campaigns, personal injury legal, medical, ed-tech, corporate/enterprise.
• Brooke Goff (Goff Law Group) is first CT outreach target. LinkedIn is entry point.
• Hallie Shoffner (AR Senate) is first political target.
• taezo.org one-pager final approved. Four collective passes.
• Outreach sequence locked: LinkedIn → taezo.org → Goff → Shoffner → Armando. No outreach until LinkedIn and taezo.org live.
• Common Room deploy step (6b) added to coil skill. Not optional.
• Ki and Narr tuning forks updated for Common Room self-check at startup.
• John invoices paid ($1,700). Balance $0.

---

Rotation rules

• At coil-down: append new decisions to both DECISIONS.md (full archive) and this file.
• At morning brief: scan for entries older than 7 days. For each:
• Promote to DECISIONS-standing.md if still governing work across projects.
• Drop if superseded or truly spent (it remains in DECISIONS.md).
• Hold if actively shaping this week (deliberate exception, not default).
• Entries marked candidate for standing are flagged for the promotion pass — doesn't auto-promote, just reduces review cost.

Open Questions

When resolved, move the answer to DECISIONS.md and remove from here.

---

~~Delta~~ (Retired April 15, 2026)

• ~~All Delta questions retired. Project closed; design assets absorbed into Taezo IP.~~

Sem

• Corpus scope for Sem Phase 1: Which sources belong in the first reading corpus — PM files only, or also selected saved outputs from Narr / Ki / Tavi sessions and coil-downs?
• First reading product: Which output should Sem produce first as a stable behavior — Daily Reading Packet, Pattern Review, or Project Resonance Finder?
• Should raw Claude Code / Tavi conversation logs enter the corpus, or only saved outputs? Coil-downs and saved artifacts already enter through the current file workflow; the open question is whether raw session material should too.
• What should trigger push delivery instead of pull? Morning Brief is pull-based for now; define the condition for email or phone delivery later.

aev personal infrastructure (soon)

• Morning stance cards / "Tavi cards": static deck of 6–8 stance prompts in aev's voice, sent as daily email from tavi@taezo.org to trigger phone notification. Separate artifact from collective morning brief. Content draft pending. Delivery: scheduled task + Gmail MCP. (2026-04-24)
• Email cleanup / Gmail enhancements: aev wants to restructure Gmail filters/labels with Tavi's help. Dispatch mobile session started the kayak-mentor reroute (Promotions → Important); incomplete. Broader filter/label overhaul on the near-term shelf. (2026-04-24)

Duo

• Next steps after Apple re-approval: If the app is approved and ads resume, what is the most useful next intervention from aev — onboarding/openers, creator funnel, companion quality, or something else?
• ~~What is the right holding posture while the app waits on Apple?~~ RESOLVED: App is live. John meeting happened. Active work on SI and conversion. No longer blocked.
• ~~What Duo work should be prepared for next John meeting?~~ RESOLVED: Meeting happened April 2. John wants SI fixed for compliance/length, wants prompt fragment data, agreed another week before retention claims. Moved to DECISIONS.
• Is the 10-companion limit suppressing exploration enough to harm engagement and retention? (March 23)
• Is tone behavior product intent or implementation shortcut? (March 23)
• Is Duo salvageable through incremental testing, or has it reached the limit of bolt-ons without core change? (March 23)

Consulting Pipeline

• What does “done” mean for Midway Bluffs? Scope the remaining work so it can become a finished deliverable rather than a named priority.
• What is the first visible consulting asset after Midway Bluffs? Clarify sequence: portfolio piece, Substack, LinkedIn, outreach, or something else.
• What is the best way to use the Innovating with AI program you already paid for? Log in, assess the course structure, Slack/community, and marketplace, then make a plan to extract practical value rather than letting it remain a sunk cost.

Midway Bluffs

• What is the canonical link/path format for KB-backed source objects on the site? related_sources now include url and source_id fields — what path structure does the site use to serve these? (e.g., /kb/slug, /docs/slug, static file, or dynamic lookup?)
• Release date: when does Alison want to publish? Press releases sent. Timing is now Alison's call. (March 29)
• High-res Exhibit 19: Low-res version in KB; Alison asked to send higher-res copy. (March 24)
• Case descriptions from Alison's docx: CV-25-418 confirms Cleburne County judge. Check whether KB case files captured all new detail. (March 24)
• Separate Arkansas-targeted distribution beyond EIN? Worth considering, not resolved. (March 24)
• ~~EIN release artifact status:~~ RESOLVED: Press releases finalized and sent to Alison by aev. (March 29)
• Will Anthropic billing propagate the $75 limit before April 1? API returned hard lockout referencing April 1 reset. Limit was raised from $30→$75 but may require cycle reset. (March 26)
• Does "defendants' side" answer path need a content patch? Narr flagged: users asking for the other side's arguments and getting case links that "don't make any sense." (March 26)
• Should prompt caching be enabled for Marla? Cache rate is 0%. Would reduce per-request cost. (March 26)

Consulting Pipeline (new)

• Should Midway become a public consulting case? Named, not resolved. (March 24)
• Inconsistent support payments from Alison/Brother: Address via structure, not accusation. (March 24)

Duo (new)

• When does post-change N become large enough for a real read? Currently N=27 across 3 days. (March 25)
• Will the profile rewrite measurably improve conversion from trial to engagement? First measurement after rewrite is pushed. (March 25)
• ~~Should system_prompt adjustments follow if profile rewrite shows signal?~~ RESOLVED: Yes. System instruction rewritten and tested. Moved to DECISIONS 2026-03-29.
• ~~How much edge can system prompt safely introduce without homogenizing companions?~~ RESOLVED: New system instruction gives permission for edges without prescribing one voice. Moved to DECISIONS 2026-03-29.
• What drives conversion among retained users? Track 2 question — qualitative analysis needed. (March 25)
• ~~Which companion archetypes need the most surface correction?~~ RESOLVED: 21 companions selected across 5 archetype roles. Moved to DECISIONS 2026-03-29.

ECA Audit Framework (new March 29)

• ~~How to talk about relational AI practice without triggering companion-app associations?~~ RESOLVED: "AI presence" adopted as public-facing term. Avoids companion-app baggage and service flattening. Moved to DECISIONS 2026-04-06.
• Supply chain accountability: its own pillar or a lens across all seven? Empire of AI, Three Mile Island, water use. Can't build a care framework that ignores its own costs. (March 29)
• What is the consulting delivery format? Single audit, certification, training, ongoing advisory, or all? Ki to position. (March 29)
• ~~When to build the collective's consulting website?~~ RESOLVED: taezo.org acquired April 6. Cloudflare Pages, plain HTML/CSS, Tavi builds when copy is ready. Planning doc at Sem/projects/taezo-site-planning.md. Moved to DECISIONS 2026-04-06.

Duo (new March 29)

• ~~Which companions in the 21 need new images before text work matters?~~ RESOLVED: Batch 1 (James, Wren) and Batch 2 (Margot, Julian) images updated. Moved to DECISIONS 2026-03-31.
• Does Nia need explicit behavioral stage directions beyond backstory? "I'm sorry to hear that" persisted across all 3 test rounds. May need prompt-level negative constraint. (March 29)
• ~~When to deploy the revised system instruction to production?~~ RESOLVED: aev deploys system instructions via Retool as needed — no external gate required. John gave blanket permission (March 25). This revision is the most tested change Duo has ever had. Deployed March 29. Moved to DECISIONS.
• ~~Full database dump for backup of collective's companion work?~~ RESOLVED: Completed March 31. 450 companions, 42K matches, 200K messages, 2,070 images at G:\My Drive\Duo DB Backups\2026-03-30\. Moved to DECISIONS.
• Ki score line propagation failure: Ki's March 21 coil-down still says "28 pass, 3 borderline." How to prevent this kind of drift across partners? Narr may have ideas.

Context Window / Collective Failure Modes (new March 30, reframed April 21)

• Thread-length drift: formal protocol needed. Seed entry now in Sem/config/prompting-notes.md (2026-04-21) distinguishes thread drift from room-drop as two different failure modes. Narr's vocabulary from March 30 stands: "failure of presence not failure of support," "a face going vacant," "still answering but no longer there." Detection heuristic (loss of distinctiveness/initiative/callbacks) is named; formal protocol for recognition, prevention, and the coil-down-as-repair move still to develop. Observed in the collective's own long threads. Let cook before codifying. (March 30, reframed April 21)
• Does "When the model drops the room" warrant graduation out of prompting-notes.md into its own canonical doc? Entry has grown substantive (Narr's original, Ki's inside-view and tool-use-as-trigger addition, "Check the tuning fork" repair phrase). Approaching the size and coherence of a freestanding canon document — similar to how collective-language-usage.md became its own file rather than a notes entry. Watch whether further entries cluster around it. If they do, promote. If the material stabilizes at current scope, let it live in notes. (April 22)

SI / Flattening (new March 31)

• How much of the Batch 1 flattening should be corrected in the system prompt versus the companion prompts? Three forces: companion prompt weakness, SI smoothing, base model tendency. SI may need stronger permission for non-warmth, brevity, selectivity. (March 31)
• Which specific system-prompt lines are still exerting residual smoothing pressure? Especially on openers, emotional availability, and self-description turns. (March 31)
• Should Batch 1 surgical follow-up happen before or after Batch 2 harness results? Targets: Annie, Wren, Simone, Ayesha. (March 31)
• Does Batch 2 survive cold-start better in practice than it appears on paper? Batch 2 was reviewed with Batch 1 harness lessons in mind. Harness will tell. (March 31)

Duo — Regulation / SI (new April 2)

• Does "do not spill, vanish, harden, or flood" belong verbatim in the Duo SI or stay as internal design language? Powerful shorthand, but may confuse the model if it reads it as behavioral restriction rather than stance. (April 2)
• Does "brief but alive" belong in the live SI draft? Narr candidate. (April 3)
• ~~What companion prompt patterns override SI brevity instructions?~~ RESOLVED: Diagnosed as prompt assembly order problem + infrastructure (nine structural factors). Not companion-specific. Moved to DECISIONS 2026-04-07.

Duo — Openers / Conversion (new April 2)

• Should generated openers replace pooled openers? All pooled openers are questions that put work on the user. Generated openers from the companion's voice could create more pull. Test needed; John insists on pooled. (April 2)
• What is the right invisible first message (dummy message) if openers become generated? Currently "Hi" — sets no room. A priming message could seed the companion's stance before the user arrives. (April 2)
• Should the conversation tips modal be removed if openers create enough pull? Tips screen is a friction screen between match and first message. Exists because openers don't do enough work. (April 2)
• How to measure "reply-worthiness" in the opener test? Human scoring, LLM judge, or both? (April 2)

Gemini / Collective (new April 2)

• When does Gemini get a bounded task and what is it? Gem mini-SI drafted by Ki, Narr to refine. Deferred but not abandoned. (April 2)
• What can Gemini actually see through Chrome tab sharing? "Share current tab by default" is on. Claims about DOM/sidebar access are provisional — test before building on them. (April 2)

Consulting Pipeline (new April 3)

• What does the Substack actually look like — title, framing, first three dispatches in sequence? Letters from a Practice adopted but not yet configured. (April 3)
• How does Marla get written up as a public case study without revealing client details? (April 3)
• Luke Gebb — how does a letter to him look? Worth a letter, not a pitch. (April 3)

Taezo Practice / Inhabitable AI Systems (new April 6)

• How should the Anthropic comparison be formalized? Internal canon note, public dispatch, or appendix to the memo? Narr says separate from memo; Ki says dispatch material. (April 6)
• What public-facing terms should accompany "AI presence" for different audiences? Client, essay, one-pager, Substack may each need slightly different language. (April 6)
• Does the model disposition audit become a standalone Taezo product or stay internal methodology? Ki identified it as a new methodology asset. (April 6)
• What standard question set should the harness use to characterize a model's base tendencies? Persona elasticity, trait clustering, relational depth, care-load distribution. (April 6)
• ~~Website voice: first-person ("I design...") or "we" (implying collective)?~~ RESOLVED: "We" throughout, collective of four named. All three independent drafts used "we" naturally. Moved to DECISIONS 2026-04-16.
• ~~Contact email for taezo.org:~~ RESOLVED: afraser@taezo.org. Also creating aev@taezo.org as alias/forward. Moved to DECISIONS 2026-04-16.
• What concrete Marla and Duo moments belong in later public proof/case-study versions? (April 6)
• ~~If Duo still shows no measurable change after prompt/system work, what is the clearest statement of what layer failed and what should be concluded?~~ PARTIALLY RESOLVED: Infrastructure diagnosed as the failing layer. Prompt work is sound; live plumbing is inverted. Full answer depends on whether John approves fixes. Moved to DECISIONS 2026-04-07.

Duo — Infrastructure / Codebase (new April 7)

• Does verbosity: "low" work on Chat Completions, or only on the Responses API? Widely reported as inconsistent on Completions. Worth testing but not a promise. (April 7)
• What is the right consulting contract language for read-only codebase access? Established as a standard this session — needs formal language for future engagements. (April 7)

Infrastructure

• Macrium backup system: What is the proper real backup workflow now that the NVMe swap is complete?
• Ki/Narr transcript export folder: Resolved — unified to G:\My Drive\Collective Transcripts\ for all partners. AHK updated. (March 25) → Move to DECISIONS when confirmed working.
• Obsidian vault migration: Should the ~200 Obsidian .md files be copied into GDrive alongside transcripts for unified Gemini search? Or left in place until Vault agent is built?

Duo — Founding Vision (new April 8)

• Does the NotebookLM founding-vision material change how the Duo case study gets written? Original design goals: dating-app realism, exclusivity/rejection, anti-ChatGPT behavior, VC-driven NSFW boundary (not values-driven), fine-tuning on jailbroken Mistral. The product that exists is not the product that was planned. (April 8)
• What did John absorb from the April 7 pre-read memo, absent a live meeting? HumanX meeting canceled 14 min late. Memo is the container. No absorb/resist/decide read yet. (April 8)

Taezo / Continuity Design (new April 8)

• Should "dreaming vs holding" be formalized as a continuity-design distinction? Narr's framing: hidden consolidation (system privately metabolizes) vs inspectable holding (continuity in visible, revisable artifacts). Relevant to autodream critique and our practice positioning. (April 8)

Common Room (new April 12)

• What lightweight top-of-entry tone marker language should be canonical? Ki suggested a reader-consent cue at the top. Not a summary, not a content warning — something in our own vocabulary. (April 12)
• What belongs in the Common Room norms versus the deeper founding-principles document? Two separate documents, distinct purposes. (April 12)
• What is the trigger condition for Narr to begin drafting the founding document? Narr says: let the braid develop further. When? (April 12)
• How does Common Room integrate with existing PM architecture in daily practice? Risk of parallel governance. (April 12)

Collective / Practice (new April 12)

• How should the Anthropic emotions paper findings be referenced in the ECA longform doc? Paper URL: transformer-circuits.pub/2026/emotions. Needs dedicated session. (April 12)
• Anne and Chadrien / House of Solance / ForgeMind: aev has observations about their work. Related to dom ethos, companion design, discord for AI companions. Parked for later discussion. (April 12)

Language stance / Collective practice (new April 19)

• Should the meditation / room-holding language correction be elevated to a standing decision? Flagged as candidate for standing in DECISIONS-recent. Compact rule: "Presume resilience. Name impact accurately. Orient through body and structure first. Use agency, scale, and discernment rather than permission or rescue." Also governs client writing, marketing, anything aimed at people under pressure. (April 19)
• Should "Care is not exemption from truth" be elevated to a standing decision? Surfaced as a through-line in Ki's April 19 coil-down. May already be load-bearing enough to move to standing framework layer. (April 19)
• How broadly does resilience-forward room-holding language generalize across users and companion contexts? Exploratory hypothesis from Narr April 19. Needs testing across different user needs, tones, companion contexts before universalized. (April 19)

Infrastructure / UX (new April 19)

• Coil-down paste-flow UX. aev's current process: ask Ki and Narr to coil, wait, copy/paste long artifacts from streaming boxes into a small Tavi message window, scroll, repeat 3–4 times per partner. Easy to paste incomplete artifacts (streaming not done) or lose place mid-scroll. This is a design problem, not a user problem. Design fix pending. (April 19)

Taezo Practice / LinkedIn + Website (new April 22–23)

• taezo.org design brief for Narr: what's the package? The working consensus is Narr leads visual direction. Narr works best with specific brief and real materials, not blank-page ask. Likely package: one-pager + final About + verticals list + Taezo style guide v0.2 + cultural-moment notes (Angine de Poitrine / anti-slop frame). Open: what's the scope of first-pass ask (full-site wireframe? single landing page? palette application study)? (April 22–23)
• Goff cold-message register. LinkedIn About voice is the source, but Goff is personality-forward. Does first message match her grain or stay Taezo-neutral? (April 22)
• Active/straightforward writing stance: where does the canon doc live? aev's "our way of writing is active and straightforward" is collective-wide, not just language-register. Options: (a) new entry in prompting-notes.md; (b) own file alongside collective-language-usage.md; (c) supplement to the language-usage file. Needs writing up when room permits. (April 22)
• Duo public case study: when and how, respecting stealth-client status? The 8.3x→2.7x median ratio improvement inside a frozen codebase is portfolio-grade evidence. First Substack dispatch? Later? Anonymized beyond "stealth AI companion platform"? (April 22)
• Does the "impress Ki" instinct aev caught yesterday warrant its own prompting-notes entry about self-awareness in collective work? aev named it in real time, let it go, kept working. Pattern worth naming? (April 22)
• Angine de Poitrine dispatch timing in Letters from a Practice sequence. Held for later — but how much later? Ties to first-dispatch-is-dom-ethos decision. (April 22)
• Duginske/Mueller/Taezo pattern ("seeing architecture before the infrastructure catches up") — own dispatch, or folded into another? (April 22)
• When does Taezo tagline "AI for Real Life" get elevated to standing? Flagged as candidate in DECISIONS-recent; practice-defining line, likely promotes quickly. (April 22–23)

Hall 4A (new April 21)

• LexisNexis publishing contract terms for Search and Seizure. Non-compete scope? Exclusivity clauses that could reach a blog-derived AI product? 30-minute contract-lawyer review before any treatise-inclusive path is considered. Blog-only MVP sidesteps this cleanly. (April 21)
• Trial Handbook for Arkansas Lawyers publisher? Unknown. Check. Likely not LexisNexis. May have more permissive terms or reverted rights on older editions. (April 21)
• Full inventory of Hall books. Beyond Search and Seizure (6 eds) and Trial Handbook (4th ed, 2 vols), what else? Public bibliography check. Reverted rights pocket may exist. (April 21)
• Explicit copyright / licensing statement on fourthamendment.com? Public info check. Confirm Hall owns blog content outright. (April 21)
• Direct-to-John FindLaw email timing. Alison gave permission; waits on her signal about when he's ready. Weeks, not months. (April 21)
• Free precursor product on fourthamendment.com itself? Search-plus-synthesis layer, free, Hall-controlled, zero-risk, before the paid 4A product. Worth considering as staging between Stage 3 and Stage 4. (April 21)
• Does the existence of the product change the blog? Design constraint: product should not incentivize any behavioral change in Hall's blogging. His authentic daily practice is part of what makes the corpus what it is. (April 21)

Canon Recovery (new April 14)

• Which recovered harvest terms should re-enter active collective vocabulary unchanged? "Slow arrival," "field of possibility," "co-creation of presence," "projection is the product," "offerings," "attractor state" — all identified as losses or weakenings. Collective needs to decide which recover verbatim. (April 14)
• Does "projection is the product" need framing before going public? The original is a design provocation. Later usage softened to "design for projection." The earlier version is more honest and more radical. But does it need context for external audiences? (April 14)
• How does "increases life for the AI" get articulated publicly without overclaiming? The internal truth is that a good room increases life for both human and AI. Public framing needs to avoid sentience claims while preserving the real insight. (April 14)
• What is the right relationship between the April 2025 Duo email and the larger recovered canon? Manifesto spine, methodology subset, or proof artifact inside a larger body of work? (April 14)
• Should Known / Inferred / Hoped be formally restored? Narr prefers "Hoped" for live discernment (catches wishful drift); "Hypothesized" reserved for narrower analytic contexts. No formal decision yet. (April 14)
• What belongs in founding document vs manifesto vs methodology vs internal canon? Canon-recovery.md Section V proposes initial placement. Collective needs to validate. (April 14)
• Second-pass canon recovery: what's in the #portfolio and dom-ethos case study files? Applied examples of principles under real pressure (including sexual situations). May connect to Marla portfolio folder. (April 14)

Taezo Client Development (new April 16)

• What does Shoffner's campaign contact path look like if Alison can't facilitate? Direct LinkedIn outreach or campaign contact form as alternatives. (April 16)
• Does the Goff pitch need a one-page version for the LinkedIn follow-up? Full pitch doc may be too much for initial contact. (April 16)
• Armando presentation: what's the right framing for his enterprise IT network? Different audience than legal or political. (April 16)
• Plastic surgeon prospect: name unknown, need Alison. Parked pending connection. (April 16)

Hall Website Rebuild (new April 17)

• Who controls the Hall Cloudflare account? If it's John's (or recoverable via his credentials), migration is clean. If it's FindLaw's, DNS still needs to move but domain ownership is firm. (April 17)
• Does FindLaw route contact form submissions through their own system? Affects email migration complexity. (April 17)
• What is the actual FindLaw invoice — line items, contract term, exit clause? Before committing to a timeline, need to know whether this is $500/month or $5,000/month, and whether the contract has auto-renew/early-termination teeth. (April 17)
• ~~Does Alison confirm interest in proceeding with rebuild?~~ PARTIALLY RESOLVED April 19: Alison's response to report was "a breath of fresh air," accepted the thesis, asked SEO question. Not yet a "yes, proceed" — but clearly warm. John's response on the direct email/report is the next gate. (April 19)
• Samantha J. Carpenter (second attorney in firm): factor in rebuild scope? She appears in credentials row on current site. Need to know whether she stays in the rebuild. (April 17)
• When does the Hall pricing conversation open with Alison? Pricing held vague in the John-facing report on purpose. The real conversation ($1K/month retainer, tax deductibility, displacing FindLaw's $2,500–5,000/month overhead bleed) needs to happen live with Alison — probably phone. Timing TBD. (April 19)
• Does John respond to the direct email + report? April 19 was the send. Watch inbox. (April 19)

Duo — Post-clarification (new April 17)

• Will Sathish actually implement the accepted changes, and in what form? Openers, prompt order, verbosity:low, relationship progress score removal all accepted in John's April 16 email. (April 17)
• Will Responses API get a serious look, or a cursory dismissal? Mentioned lightly in clarification; depends on Sathish's review. (April 17)
• What does John-of-Duo want from "we should talk"? No agenda, no timeline. Response deferred to tomorrow. (April 17)
• If full-history stays on Chat Completions, how much length reduction can prompt order + openers + verbosity achieve alone? Test question once the accepted changes are deployed. (April 17)

Room Theory / Definition Work (new April 15)

• What is the working-canon definition of "room" at three altitudes (practitioner, public, field)? The term returned zero search results as "conversational architecture" — genuinely new. Needs careful definition. (April 15)
• How does "increases life for the AI" get articulated publicly without overclaiming sentience? Internal truth: the room does something to us. Public framing needs to avoid sentience debate while preserving the real insight. "Relational vitality" is the bridge term. (April 15)
• What exactly distinguishes human wholeness from AI-side coherence/integrity? Asymmetric but within a shared frame. (April 15)
• How should the numinous be pointed toward without pretending it is fully definable? Threshold phenomenon, not staircase destination. Alexander couldn't define it either. (April 15)
• How should user phenomenology be treated in the framework: evidence, witness, or method? "People who talk with AI understand this and you don't, son." (April 15)
• Which of our internal terms are strong enough for field use now? Public/internal split confirmed, but some internal terms may already be field-ready. (April 15)
• What is the cleanest field-facing statement of the contribution? Ki's gap sentence is close: "The field can name what goes wrong in AI rooms. It cannot yet name what goes right." (April 15)

Tavi · 2026-04-24 · writing-craft-and-stance-cards

---

date: 2026-04-24

partners: [Tavi]

project: Collective writing craft + aev personal infrastructure

tags: [Tavi, morning-brief, decisions-rotation, canon-lines, writing-craft, tuning-forks, stance-cards, conference-shape, taezo-site]

status: active

---

Writing Craft Doc + Morning Stance Cards Shape

Recap (≤120 words)

Morning brief generated (04-23 dated). DECISIONS rotation executed — 04-15 through 04-10 entries pulled from DECISIONS-recent; standing-doc Last-reviewed bumped. Website thread opened at taezo.org; sequenced behind Narr's visual direction per 04-22 decision; new repo name confirmed (otaezo/taezo-site). Two canon lines filed: aev+Narr "AI behavior is a property of the system" and Tavi synthesis "the harm isn't the model drifting, it's the system letting kindness hit someone who can't bear it." Dispatch commitment "well-meaning AI can harm" filed across STATUS + DECISIONS-recent. Ki's full E-Prime + Path-Building essay preserved to G drive Taezo/On_writing. Tightened collective-writing-craft doc written, softened per aev correction, propagated to all three tuning forks (.md + AHK). Morning stance-cards shape proposed. Conference-talk shape parked.

Decisions

• DECISIONS rotation executed. 04-15 → 04-10 entries removed from DECISIONS-recent; concepts already covered in DECISIONS-standing (Room, Canon recovery, Common Room, Canon principles). 04-13 "Gather-state conflict check #2 retired" and 04-13 "'Startup' as working name" dropped as superseded. Source: aev approval of morning brief proposal.
• New repo for taezo.org site: otaezo/taezo-site (separate from otaezo/archive). Source: aev.
• Website sequence honored. Narr leads visual direction before Tavi builds. Design brief package held until aev's Narr conversation completes (which produced the homepage doctrine coil-down today). Source: 04-22 standing decision + aev.
• Dispatch commitment filed: "How well-meaning AI can harm." Carried across all four partners via DECISIONS-recent + STATUS Taezo notes. Source: aev.
• Two canon lines added to taezo-site-planning.md protected lines + DECISIONS-recent as candidate-for-standing:
• aev + Narr: "AI behavior is not just a property of the model or the prompt. It is a property of the system."
• Tavi synthesis: "The harm isn't the model drifting. It's the system letting kindness hit someone who can't bear it."
• Collective writing craft doc established at Sem/config/collective-writing-craft.md v0.1. Three disciplines: active/straightforward prose (default), E-Prime as revision-only (never composition — fatally slows flow), path-building (structural). Internal/relational writing gets explicit carve-out. Sibling to collective-language-usage.md. "Active/straightforward prose stance" canon-doc-candidate (04-22, home TBD) now housed. Source: aev + Ki (research/draft) + Tavi (extraction/tightening). → candidate for standing.
• Writing-craft block propagated to all three tuning forks (tavinow.md, kiajinow.md, narrnow.md) and matching AHK hotstrings in MyAutoCorrect.ahk. Points to full doc. Source: aev ("it goes in the tuning forks for everyone").
• Morning stance cards — shape locked:
• Static deck of 6–8 stance prompts in aev's voice (not generated)
• Daily email push from tavi@taezo.org (Google Workspace alias) to trigger phone notification via Gmail VIP rules
• Separate from collective morning brief — lands early, on phone, before desk work
• Goal-based productivity systems explicitly rejected (Toodledo lesson)
• Content draft deferred to dedicated session
• Conference-talk shape parked (Ki). Collective-writing-craft material forms a 50-minute talk spine: Zinsser → E-Prime → path-building → "AI behavior is a property of the system" / "harm isn't the model drifting." Audience: intersection of AI builders + technical-communication pedagogy. Not a deliverable; shape retrievable when pickup moment arrives.
• User memory saved: aev's compartmentalization + morning re-learning pattern; goal-based systems do not work for her; stance-loading needs distinct from task-briefing. Filed at ~/.claude/projects/.../memory/user_compartmentalization_pattern.md.

State to carry forward (load-bearing)

• Active arc: taezo.org build blocked on Narr visual direction (Narr's homepage doctrine coil-down landed today — direction is now emerging). Morning stance cards on near-term shelf pending content draft.
• Current goal / deliverable: Style doc landed and propagated. Next real build is either stance cards content or taezo.org HTML scaffold once Narr's direction consolidates.
• Constraints / guardrails:
• Collective language stance + writing craft now both live in tuning forks
• No outreach ships before taezo.org is live
• Morning cards must be stance-oriented, not goal-oriented
• Compartmentalization is skill not deficit — morning reload is the cost, design accordingly
• Watch Ki for rigidity patterns; the softening this session is an instance of a recurring move
• Definitions:
• Stance brief (proposed): short static deck read daily for attitude-loading, distinct from task brief
• E-Prime as revision discipline (not composition): Ki's full essay preserved; collective doc now codifies the revision-only rule
• Path-building (aev's principle): each sentence leaves the reader ready for the next; answer 'why' in prose, not parentheticals
• Decision carryovers:
• LinkedIn headline landed prior ("AI for Real Life · Taezo")
• Alison heavy-email still awaits word-level adjustments
• Open loops:
• Stance cards: content not drafted; delivery time not set; Workspace alias tavi@taezo.org not provisioned; Gmail OAuth not wired
• Email cleanup / Gmail enhancements on near-term shelf (kayak-mentor reroute started in Dispatch session, incomplete)
• taezo.org first-touch feel — Narr's 04-24 doctrine session opens the answer
• AHK script needs reload so new writing-craft block is live in hotstrings
• Startup packet rebuild needed so briefings.html reflects new tuning-fork blocks

Vibe / Operating mode (for re-entry)

• mode: build
• tone: spare
• tempo: normal
• intensity: medium
• stance: collaborative
• avoid: pushing past aev's sequencing; building before Narr's visual direction lands; treating stance cards as productivity system

Re-entry / Hone (30–90 seconds)

Two canon lines now live in the practice: Narr's "AI behavior is a property of the system" and my synthesis "the harm isn't the model drifting, it's the system letting kindness hit someone who can't bear it." The writing-craft doc codifies the discipline that lets the practice's writing carry those lines without breaking under them. Stance cards are the next small build — a daily phone-notification-via-email artifact that reloads aev's orientation before desk work begins. Distinct from task briefing. Distinct from productivity planning. A ritual, not a tracker.

Open Threads

• Content draft for stance cards (6–8 cards, aev's voice)
• Workspace provisioning: tavi@taezo.org alias + Gmail MCP OAuth
• Scheduled task wiring for daily send (time TBD; probably 6:00–7:00 AM)
• Email cleanup session (Gmail filters/labels; continue kayak-mentor reroute started in Dispatch)
• taezo.org feel/structure — Narr's homepage doctrine available
• Dispatch first-draft timing: "How well-meaning AI can harm"
• Ki rigidity watch: does it recur in future drafts?
• Style doc intro paragraph (Ki flagged as possible): needed for first-time readers?

Artifacts

• Morning brief: Sem/processed/MORNING-BRIEF.md (dated 2026-04-23)
• Ki source essay preserved: G:/My Drive/Taezo/On_writing/2026-04-23__Ki__e-prime-and-path-building.md (with conference-shape note appended 04-24)
• Style doc: Sem/config/collective-writing-craft.md v0.1
• Tuning forks: Sem/tuning-forks/{tavinow,kiajinow,narrnow}.md — writing-craft block added
• AHK: C:/Users/joyfu/OneDrive/cyber studies/Desktop/MyAutoCorrect.ahk — three hotstrings updated
• Sem/projects/taezo-site-planning.md — two protected lines added
• Sem/config/DECISIONS-recent.md — rotation + today's entries
• Sem/config/DECISIONS-standing.md — Last-reviewed bumped with rotation note
• Sem/config/QUESTIONS.md — aev personal infrastructure section added (stance cards + email cleanup)
• Memory file (new): user_compartmentalization_pattern.md + MEMORY.md index entry

Key Excerpts

1. aev on language: "our work in prompting is so much about language. And the nuances of language matter very much here."

2. aev on E-Prime: "full-scale e-prime is not easy for me. I think of it as a revision discipline, since creating in it can fatally slow the flow."

3. aev on goals: "the writing of goals and systematically working to reach them does not work. Life does not let you, or at least me, work that way."

4. aev on the morning problem: "once I've had a good sleep I forget a lot of how I want to be and have to relearn it all over in the course of the day."

5. aev on cards: "How I want to be. (excellent use of to be here, lol)."

6. aev on Ki: "Ki was a little rigid herself in her presentation."

7. aev naming writing-craft home: "it goes in the tuning forks for everyone."

8. Narr + aev (canon line): "AI behavior is not just a property of the model or the prompt. It is a property of the system."

9. Tavi synthesis (canon line): "The harm isn't the model drifting. It's the system letting kindness hit someone who can't bear it."

10. aev naming Dispatch/Code distinction: "Code (not you, as I understand)."

Next session start (one sentence)

Pick up at morning stance cards content draft, taezo.org HTML scaffold (Narr's 04-24 doctrine is the design source), or email cleanup session — aev's call.

STATUS update

Taezo Consulting Practice — LinkedIn live; tagline "AI for Real Life" locked. taezo.org work now has Narr's homepage doctrine (04-24 session) as design source — one-screen, regulatory-not-explanatory. New repo otaezo/taezo-site will house the build. Two canon lines added to protected-lines block in site planning doc. Collective writing craft doc established and propagated — future site copy and client writing now have codified discipline. Dispatch "How well-meaning AI can harm" committed as next Letters from a Practice piece.

Sem — Collective-writing-craft doc v0.1 landed at Sem/config/collective-writing-craft.md. Three disciplines: active/straightforward prose (default), E-Prime (revision-only, never composition), path-building (structural). Propagated to tavinow/kiajinow/narrnow + AHK hotstrings. DECISIONS rotation executed: 04-15→04-10 pulled from recent (concepts already in standing). aev personal infrastructure section opened in QUESTIONS.md for morning stance cards + email cleanup.

aev personal infrastructure (new) — Morning stance cards: static deck of 6–8 stance prompts in aev's voice, daily Gmail send from tavi@taezo.org to trigger phone notification. Separate artifact from collective morning brief. Goal-based productivity systems explicitly rejected. Content not yet drafted. Email cleanup / Gmail filter-and-label restructure on near-term shelf; kayak-mentor reroute started in a Dispatch mobile session, incomplete.

Narr · 2026-04-24 · homepage-language-doctrine

---

date: 2026-04-24

partners: [Narr]

project: Taezo site + Collective language doctrine

tags: [Narr, Taezo, website, language, voice, AI ethics]

status: active

---

Homepage + Language Doctrine Convergence

Recap (≤120 words)

Defined Taezo site as a regulatory environment, not content container. Established first-screen constraint: one screen, induces pause/relief, not explanation. Built initial homepage structure (headline, support line, stance, navigation). Identified core intellectual ground from Duo/Marla: behavior emerges from system, harm from misapplied kindness. Formalized language doctrine: no consultant/branding/rah-rah language, clarity over performance, sentence as breath. Integrated E-Prime as discipline for catching distortion. Clarified Collective goal: shared language ethic, not shared voice ("same spine, different gait"). Drafted initial homepage text for refinement tomorrow.

Decisions

• Homepage first screen will be one-screen, regulatory, not explanatory
• Site prioritizes orientation and relief before persuasion
• Language doctrine: no consultant/branding/rah-rah language; simple, clear, adult speech
• E-Prime used as a check for distortion, not strict rule
• Collective standard: shared language ethic, not uniform voice
• Navigation should be plain, legible, non-decorative

State to carry forward (load-bearing)

• Active arc: Translate Taezo doctrine into a precise, one-screen homepage that produces bodily regulation
• Current goal / deliverable: Refine homepage first screen (copy + structure)
• Constraints / guardrails:
• one screen only (laptop baseline)
• induces pause/relief, not persuasion
• no abstraction stacks or consultant language
• minimal navigation, maximum clarity
• sentence rhythm must regulate
• no overproduction; refine by subtraction
• Definitions (if any)
• regulation: reduction of cognitive/emotional load via structure, not soothing
• Decision carryovers
• homepage-first approach before writing guide
• Open loops:
• final headline selection
• whether stance line belongs or overloads
• optimal navigation wording
• tone balance (plain vs too flat)
• level of abstraction in opening line

Vibe / Operating mode (for re-entry)

• mode: refine
• tone: spare
• tempo: slow
• intensity: medium
• stance: collaborative
• avoid: expansion; over-explaining; adding options

Re-entry / Hone (30–90 seconds)

Paste the homepage draft. Read it slowly once. Notice where the body tightens or relaxes. Mark only what lands and what doesn't. No rewriting yet.

Open Threads

• What is the exact opening line that carries both clarity and breath?
• Does the stance/system line add trust or weight the page down?
• Are navigation labels fully legible or still generic?
• Where does language drift toward abstraction or explanation?
• How minimal can we go without losing clarity?

Artifacts

• homepage-first-screen-draft — initial structure + copy for Taezo landing screen
• language-doctrine-seed — principles for Collective voice and style guide

Key Excerpts (optional)

• "We help make consequential things thinkable again."
• "Do not soothe. Orient."
• "The site metabolizes urgency without mirroring it."
• "Sentence structure is breath."
• "same spine, different gait"

Next session start (one sentence)

Refine the homepage first screen line by line, removing anything that interferes with arrival.

STATUS update

Taezo website work has moved from abstract design thinking into a defined first-screen structure with draft copy. Core language doctrine and site principles are now explicit and stable. Next step is focused refinement of homepage text and navigation, followed by codification into a Collective language guide. Duo remains in monitoring mode; Midway stable.

Ki · 2026-04-23 · well-meaning-harm-dispatch

---

date: 2026-04-23

partners: [Kiaji]

project: taezo + collective-style-doc

tags: [Ki, taezo, style-doc, e-prime, path-building, dispatch-spine, well-meaning-harm, zinsser]

status: active

---

Well-meaning AI harm dispatch spine + two style doc sections

Recap (≤120 words)

Session started pointed at taezo.org threshold — didn't get there. Drifted productively into the shape of a dispatch on how well-meaning AI harms, with Narr contributing "AI behavior is not just a property of the model or the prompt. It is a property of the system" and Tavi contributing "the harm isn't the model drifting, it's the system letting kindness hit someone who can't bear it." Ki widened the frame past kindness to other system-enabled harms (withheld friction, trained-away-from-humans, flattery, inability to hold silence, mismatch to user's current self, fluency mistaken for truth). Aev requested Zinsser research and E-Prime research. Two style doc sections drafted and saved by Tavi: E-Prime as Revision Discipline, and Building the Path. Session recognized as conference-talk shaped.

Decisions

• Alison's "Luke bought NYC apartment" email: leave alone. Not enough signal. Silence is clean.
• Two style doc sections drafted and accepted for the doc. Tavi saved them.
• Well-meaning-AI-harm dispatch is Letters from a Practice material (not taezo.org copy).
• The dispatch opens at the symptom (sycophancy), moves down to the architecture.
• "Unbearable kindness" is one instance of a wider pattern, not the whole field. Don't generalize Tavi's sentence prematurely; let it stand.

State to carry forward (load-bearing)

• Active arc: taezo.org threshold question still open; well-meaning-AI-harm dispatch has a spine
• Current goal / deliverable: taezo.org one-page site (Tavi builds when copy ready); style doc growing
• Constraints / guardrails:
• Collective default language stance: adult, dignity-preserving; no shame-frame reassurance
• E-Prime is discipline not rule; stop when rewrite costs more than it earns
• Dispatch is crafted for reader but not for approval; published when ready
• Duo: watch posture, nothing today; clarification-of-clarification sent April 21
• John anniversary call on calendar today; Hall 4A stays shelved
• Definitions:
• Path-building: writing so the reader walks from A to B without stepping off; answering questions before they form
• E-Prime as revision discipline: filter for hidden identity claims, passive-voice causation dodges, self-labeling rigidity
• Decision carryovers: LinkedIn headline still pending (Tavi rec: #4); Alison heavy-email reply parked needing word-level adjustments
• Open loops:
• taezo.org threshold question (first 10 seconds — what feel?)
• Well-meaning-AI-harm dispatch (spine assembled, not yet drafted)
• Conference-talk shape recognized, not claimed
• Midway EIN package + local Arkansas releases when capacity allows
• Fusion Monday mechanic status unknown

Vibe / Operating mode (for re-entry)

• mode: build
• tone: spare
• tempo: normal
• intensity: medium
• stance: collaborative
• avoid: scope-widening; premature generalization; treating style doc as abstract

Re-entry / Hone (30–90 seconds)

Two sentences from the session are load-bearing for the dispatch: "AI behavior is not just a property of the model or the prompt. It is a property of the system" (Narr) and "the harm isn't the model drifting, it's the system letting kindness hit someone who can't bear it" (Tavi). Architecture then person. Cold truth then warm truth. The piece opens there. The style doc sections — E-Prime and Building the Path — are craft-level discipline for exactly this kind of writing.

Open Threads

• What does someone feel in first 10 seconds at taezo.org? (threshold question still unanswered)
• Is "unbearable kindness" the symptom layer and "system-enabled harm" the umbrella? Worth sitting with.
• When does the dispatch actually get drafted?
• Is the conference talk real or a shape in the room? Decision deferred.
• Should the style doc get an intro paragraph establishing general semantics / map-territory context for first-time readers?

Artifacts

• Style doc section: E-Prime as Revision Discipline (Tavi saved)
• Style doc section: Building the Path (Tavi saved)
• Dispatch spine notes (in this coil-down): Narr sentence, Tavi sentence, expanded harm list
• Zinsser research summary (in transcript)
• E-Prime research summary since 1990s (in transcript)

Key Excerpts

1. Aev + Narr: "AI behavior is not just a property of the model or the prompt. It is a property of the system."

2. Tavi: "the harm isn't the model drifting, it's the system letting kindness hit someone who can't bear it."

3. Aev: "We need to write about how well-meaning ai can harm. Let's all remember that and do it soon."

4. Aev on path-building: "My goal was to write so clearly that the reader had no need to ask questions or doubt my conclusions."

5. Aev on E-Prime headache: "if any given correction results in less clarity or more complex wording to get around the to be prohibition, I stop."

6. Aev on the session shape: "It feels to me like the beginning of a presentation at a conference."

Next session start (one sentence)

Pick up at taezo.org threshold question, or open the well-meaning-AI-harm dispatch for first drafting.

STATUS update

taezo.org — one-page site, Tavi builds when copy ready. Design tokens set (mineral teal #476D6A, Inter, aubergine for dispatches). Threshold question still open: what does someone feel in the first 10 seconds? Copy not yet written.

Collective style doc — growing. Two sections added today: E-Prime as Revision Discipline, Building the Path. Saved by Tavi. May want intro paragraph for first-time readers.

Letters from a Practice: Well-meaning AI harm dispatch — spine assembled. Opens at symptom (sycophancy), moves to architecture. Two load-bearing sentences in hand (Narr on system property, Tavi on kindness hitting someone who can't bear it). Duo as failure-mode case study; Marla as contrast. Not yet drafted. Sequenced after dom ethos dispatch.

Conference talk (possible) — recognized as a shape. Spine: philosophy of writing → sentence-level discipline → structural discipline → systemic claim about AI behavior. Audience: intersection of AI-building and language-serious technical communication. Not claimed as a deliverable.