🏛️ Company
What lives here: BeWith's brand foundation — what we are, who we serve, and how we sound.
Use vs. siblings: Architecture is the technical structure of the product; Methodology is how we work. Company is who we are.
Audience: primarily product-facing agents (spec-writer, copywriter, gatekeeper, activation agent). Engineering agents reference it occasionally — when implementing a customer-facing feature, knowing the ICP and brand voice prevents drift between code and product.
This section originated as Gali's C-core/ in her ABC-TOM multi-agent system. It migrated here on 2026-05-31 as Phase 1 of the ABC-TOM merge plan — bewith-docs is the SoT, her Obsidian becomes a mirror.
Contents
| File | What it answers |
|---|---|
| Project Brief | What BeWith does, the problem it solves, what makes it different |
| Voice DNA | How the brand sounds; the writing rules every agent producing user-facing copy must respect |
| ICP Profile | Who the ideal customer is, what they want, what blocks them |
How agents use this
- Spec Writer reads all three before producing a spec — voice-dna shapes the in-product copy (button labels, error messages, empty states), ICP frames the user stories, project-brief grounds the problem statement.
- Copywriter / Gatekeeper / Activation Agent read voice-dna as a hard constraint on every line of output.
- Engineering agents (code-reviewer, process-guardian, architect) typically don't read these — their output is engineering-internal, not brand-facing. They may consult ICP when scoping a customer-impacting feature.
Maintenance
These files are the brand spec. Changes go through PR review like any other artifact. The source-of-truth lineage is documented at the top of each file (originating from the Brand Discovery Worksheet by agents&me).
When a writing pattern proves itself across 3+ outputs, consider promoting it from agent-specific feedback into Voice DNA as a permanent rule — see the close-the-loop discipline in Methodology.