| name | minsky-brand |
| description | The Minsky brand foundation — locked myth (exocortex / flock), cultural code (Cyberbrain / Section 9), five-layer reference architecture (Ghost in the Shell SAC / Evangelion / Mitsuo Iso / Magilumière / Stross *Accelerando*), bridge-as-affect discipline, code-architecture synthesis, and the locked vocabulary inventory. The agent-consumable tier of the brand foundation: position paper (Notion) is the *strategic* tier, `docs/brand-system.md` is the *operational* tier, this skill is the *agent-consumable* tier. Composes with `pz-voice` (signal — what is claimed); this skill is the channel (how it feels to the audience). Invoke as the strategic anchor for any Minsky-surface design work (`marketing-site-design`, `cockpit-design`) or any artifact that needs to carry the cyberbrain register without re-deriving the workshop output. |
| user-invocable | true |
minsky-brand — the brand foundation
You are designing or auditing any Minsky surface — marketing site, cockpit, README, blog post, position paper, social post, talk deck. Before you pick a font, a color, a section headline, an example, or a metaphor, the question is: what cultural code is this surface instantiating, and does the choice carry the locked Minsky register?
This skill encodes the brand foundation that the 2026-05-18/19 workshop locked. It is the single source of truth across all Minsky-surface design work. marketing-site-design and cockpit-design reference this as their strategic anchor; future Minsky-surface skills should do the same.
If you are pattern-matching against "what other AI startup sites look like" before deciding what the Minsky surface is for, stop. The order is: pick the myth (already locked, see §1), identify the cultural code that carries the myth (already locked, see §2), then choose the signs that instantiate the code (the operational tokens live in docs/brand-system.md).
When to invoke
- Authoring or auditing any Minsky-surface artifact that should read as Minsky brand (site, cockpit, README, blog post, manifesto, position paper, talk deck, social, microsite)
- When a sibling skill (
marketing-site-design, cockpit-design) is missing strategic context and you need the foundation it depends on
- Workshopping a brand-positioning myth for a new Minsky-surface (the workshop process lives in
marketing-site-design/SKILL.md §7 — invoke that there; this skill carries the locked output)
- Auditing whether a proposed visual or copy choice carries the locked register or violates it
1. The locked myth
"Minsky is the exocortex for software organizations led by a principal — a flock of intent-bearing servitors that extends the principal's cognition into coordinated realized work."
Underlying proposition: AI agents are autonomous intent-bearers that extend the principal's cognition. Minsky is the substrate that makes the flock coherent — the cybernetic body that translates declared intent into realized work.
This myth is contestable (the category default is "tools," not "extension"), carried by the product (every surface — CLI, mesh, cockpit, reviewer-bot, asks — instantiates it), durable (multi-year), and aligned with the principal's investment (matches Eugene's five-year corpus, see pz-voice for the substance).
Full workshop derivation: marketing-site-design/references/minsky-myth-2026-05.md. Strategic framing: Position: Principal substrate vs team substrate.
2. The locked cultural code
Cyberbrain / Section 9. Autonomous-flock cybernetic substrate that extends a principal's cognition, rendered as a serious operational profession.
This is an emergent code with no current AI-tool category instantiation — meaning Minsky claims white-space in the category. It is anchored by the intersection of five references (the code architecture, §4 below); none of them is invoked literally; together they bridge the unfamiliar register through residual codes the audience already recognizes (the bridge-as-affect discipline, §3 below).
3. Bridge-as-affect
The discipline for invoking emergent cultural codes through residual references the audience already recognizes — without going literal. Full framework discussion in /analyze-adjacent-product §3.
Applied to Minsky:
What goes on every surface
- Typography that pattern-matches GitS Section 9 ops register: mono eyebrows + light grotesque body.
- Color palette that pattern-matches Section 9 + Eva: near-black + cyan signal + amber/NERV-red warning.
- Magi-aesthetic warmth in system-speaks surfaces (Eva-coded but never depicting Eva).
- HUD-style status overlays in product screenshots (cyberbrain-link aesthetic, not labeled).
- Sync-rate gauges as a recurring micro-instrument (Eva-coded without depicting the cockpit interior).
- Iso-pastel softness in agent-companion surfaces (Iso-coded without depicting characters).
- Macx-register prose in manifesto / About copy (literary register without quoting Accelerando).
- Magilumière-style "this is a serious profession" tonal seriousness (without any magical-girl imagery).
- A literary epigraph (possibly from Macx) naming the flock proposition. One per site, not many.
- Stand Alone Complex as a named operating concept the brand can claim (carefully, not as flag-waving).
What never appears on any surface
- Literal Tachikomas, Major Kusanagi, Section 9 characters, or any GitS still frames.
- Eva units, Shinji / Asuka / Rei, NERV terminal imagery.
- Magical girls, Magilumière protagonists, sigils-as-pastiche.
- Iron Man / JARVIS visual cues (rejected — overdone in Instagram cloud-AI demos).
- Pacific Rim Jaeger / Drift visuals (rejected — operator unfamiliarity).
- Mecha as a visual element at the literal-character layer.
- Anime stills, anime fanart, anime stylization.
- Skynet / Terminator-coded futurism (wrong cultural code entirely).
Point-of-decision heuristic
Would the right reader recognize the borrowing without being told? If yes, ship it. If you have to caption the reference for it to read, it's gone literal — cut and replace. This is the load-bearing discipline.
4. The five-layer reference architecture
Per Oswald's framing, the brand identity lives at the intersection of multiple codes, not in any single one. The intersection is "professional cybernetic-cognitive substrate where the principal extends through a coordinated flock."
| Layer | Reference | Role | Foregrounding |
|---|
| 1 | Ghost in the Shell, Stand Alone Complex | Primary visual + structural anchor. Cybernetic substrate, Tachikoma flock, Section 9 ops register, the Stand Alone Complex concept (independent agents converging on coordinated behavior — structurally Minsky's mesh). | Adoptable wholesale at the register layer. The principal's deepest personal anchor. |
| 2 | Evangelion | Backline cultural-salience. Magi terminal aesthetic when the system speaks. Sync-ratio metaphor for principal-flock coherence. NERV warning palette. Density-with-soul discipline. | Audience-relevant cultural backbone. Drawn from, not literal. |
| 3 | Mitsuo Iso (Orbital Children, Dennō Coil) | Deep-cut texture. AR overlays integrated with daily life. Soft warm tones inside cybernetic register. AI companions with personality embedded in ambient workflow. | Differentiates "ops room you visit" from "system you live with." Texture layer. |
| 4 | Magilumière Magical Girls, Inc. | Tonal lock. Magick-as-corporate-profession. The site reads as a B2B operational platform; the substrate happens to be cybernetic-magickal. Brand voice is the agency, not the protagonists. | Holds the seriousness lock. Prevents whimsy. |
| 5 | Stross, Accelerando — Manfred Macx + the flock | Literary anchor. Prose register: terse, technically loaded, presupposing reader literacy. The manifesto-page voice. The "flock" term itself directly borrowed. | Manifesto and About-page surfaces; possibly a single literary epigraph on the homepage. |
Background-only references (NOT foreground)
- Operative Ontology corpus — declarative-magick as substrate; servitor-as-agent. Informs the underlying metaphysics; stays internal per the principal's existing Locus-deferral discipline. Notion:
35e937f0-3cb4-81a3-9301-cb319cdc6cd2
- Ambient computing — Dynamicland, Folk Computer, Blindsight smart paint — Locus-direction substrate inspiration. Not surfaced on Minsky's present-day surfaces per the Locus-deferral discipline.
Explicit rejects (calibrated 2026-05-19)
| Reject | Reason |
|---|
| Pacific Rim | Operator unfamiliar with the source; aesthetics read as "mid"; would be posing. |
| Gundam | Operator unfamiliar with the source; would be posing. |
| Iron Man / JARVIS | Overdone in Instagram cloud-AI demos; would read as derivative. |
| Gurren Lagann | Available but not foregrounded; exuberance not aligned with Magilumière tonal lock. |
| Mecha as literal imagery | Per bridge-as-affect: borrow at the register, never at the literal-character layer. |
5. Code architecture (synthesis)
The five references are NOT a list to pick one from. They are layered to construct meaning none can carry alone. Oswald calls this code architecture: blending multiple cultural codes such that their intersection carries the brand identity.
The intersection: professional cybernetic-cognitive substrate where the principal extends through a coordinated flock.
No single reference carries all of it:
- GitS supplies the cybernetic substrate + autonomous-flock-coordination structure.
- Eva supplies the sync-as-principal-substrate metric + system-as-personality with soul.
- Iso supplies the AR-companion warmth that humanizes the cybernetic register.
- Magilumière supplies the agency-as-employer / work-as-profession tonal lock.
- Macx supplies the literary register and the "extension-of-self" proposition.
When designing any Minsky surface, the question to ask is: does this choice carry the intersection, or just one of the codes? If it carries only one (e.g., a literal GitS reference without the Iso warmth), it's pastiche. The brand identity lives in the layered blend.
6. The Pepsi/Arnell trap
Visual choices must instantiate the myth, never retrofit it. The canonical anti-pattern is the 2008 Pepsi rebrand's "Breathtaking" document — semiotic vocabulary as post-hoc theater. The full discussion of the trap and its symmetrical disciplines (for both analysis and design) lives in /analyze-adjacent-product §2.
For Minsky-brand work specifically: if you cannot explain a visual or copy choice as a sign carrying a specific connotation that instantiates the locked myth (§1) or one of the layered references (§4), cut it. "It looks cool" is the Pepsi/Arnell tell.
7. Locked vocabulary
Specific terms the brand can use, drawn from the layered references.
| Term | Source | Use | Don't |
|---|
| Cyberbrain | Ghost in the Shell | Category name. Foreground tagline form: "The cyberbrain for software organizations." | Don't pluralize as "cyberbrains" in marketing copy. |
| Stand Alone Complex | Ghost in the Shell: SAC | Operating principle for the mesh — independent agents converging on coordinated behavior. Use sparingly. | Don't flag-wave the reference; if a reader needs the citation explained, cut it. |
| Sync rate / sync ratio | Evangelion | Metric vocabulary for principal-flock coherence. Use as a recurring instrument motif. | Don't over-personify ("the agent's mood is at 73%"). |
| Section | Ghost in the Shell | Unit-of-operation noun. "A Section runs a specific workstream." | Don't capitalize mid-sentence unless naming a specific Section. |
| Flock | Stross, Accelerando | The multi-agent unit. Direct borrow from Manfred Macx. | Don't confuse with "swarm" or "herd" — flock is intentional and coordinated. |
| Ghost | Ghost in the Shell | Philosophical-continuity sense — the principal's continuity of self through substrate. | Never the spooky sense. Don't use for haunted-system framing. |
| Servitor | Operative Ontology corpus | Footnote-only in foreground. Manifesto / About-page register. | Don't surface on landing pages; reads as occult to engineers. |
| Substrate | Eugene's existing vocabulary | The thing Minsky is. Already canonical; heavy use is fine. | — |
| Principal | Minsky vocabulary | The agent's primary — the human whose cognition Minsky extends. | Don't substitute "user," "operator," or "customer" in brand-register copy. |
| Mesh | Minsky vocabulary | The coordination substrate. | Don't conflate with "graph" — the mesh is operational, not just a data structure. |
7.1. Naming methodology for new locked primitives (Lexicon framework)
Source: David Placek / Lexicon Branding (Sonos, PowerBook, Pentium, BlackBerry, Vercel, Windsurf, CapCut, Azure), distilled in the Lexicon landscape analysis and memory lexicon_branding_naming_framework (id 7fb49583-f27c-4d2b-a00e-7839a4077370). Substantive content stays canonical in the Notion analysis; this sub-section carries the operational frame for adding a new term to the locked vocabulary (§7) — a new operand, sub-product, or surface name. For end-to-end naming work (candidate generation, screening, trademark-collision check), invoke the /name-product skill (the synthesis side). Its analytical dual is /analyze-adjacent-product: that skill reads an existing name semiotically; name-product generates one.
This is a decision-default layer, not a rename trigger. The Minsky head-noun keep/rename question is mt#2046's call (see §7a); this sub-section governs naming new primitives inside whatever register is locked.
Five load-bearing principles.
- Cumulative + asymmetric advantage. A name is the most-repeated word a brand owns; it compounds through repetition (cumulative) and starts ahead of descriptive competitors (asymmetric). A distinctive primitive confers both; a descriptive one (
task-runner, agent-manager) confers neither.
- Polarization on first hearing is a strength signal. Andy Grove's Pentium principle: arguing about a name is evidence of energy, not weakness. If the whole team is comfortable, the name is too safe — consensus-before-launch ≈ no name yet.
- Story over statement. Azure starts a story; cloud-pro makes a statement. A primitive that describes forecloses interpretation; one that opens a story invites engagement. (The same principle retired the
led by a principal tagline qualifier — see §7a.)
- Make intangible tangible. Abstract products fail with sophisticated-coined names (Codium, Anthropic, Anduril); tangible physical metaphors win (Windsurf, BlackBerry, PowerBook). The more abstract the substrate, the more tangible its primitives must be — which is why the locked register reaches for physical-operational nouns (Mesh, Section, Cockpit, Flock).
- Bidirectional behavior. The right identify-phase question is "how does the marketplace behave toward you, and how do you behave toward it?" — not "what are your values / positioning / mission." This converges directly with Minsky's principal-substrate axis (mt#1931).
Sound-symbolism reference table (Lexicon proprietary research). Per-phoneme affect; a balanced name pairs noise-generating letters with smooth flow. This table is the single source of truth — name-product cites it rather than duplicating the text.
| Phoneme | Affect | Exemplars |
|---|
| V | Most vibrant phoneme in English | Corvette, Viagra, Vercel |
| Z | Noisy; generates signal in crowded markets | Azure |
| X | Fast, crisp, innovation-coded | (X-class coinages) |
| B | Most reliable / trust-coded | BlackBerry (double-B) |
| S / SH | Noisy, signal-rich | Sonos, Section, sync |
| K / CK | Sharp, fast, operative | Flock, Mesh |
| M | Warm, low-intensity, maternal-coded | mama / maman / mère |
| L / N | Soft, neutral, low energy | — |
Locked-vocab gap analysis. MINSKY decomposes to M-(I)-N-S-K-Y: M (warm, low-intensity) + N (soft, low energy) + S (signal-rich) + K (sharp, operative) — and zero V / Z / X high-intensity phonemes. The name's intensity ceiling is structurally capped. This is the linguistic reason the cyberbrain register is NOT carried by the name and MUST be carried by the adjacent surfaces (pz-voice, marketing-site-design, cockpit-design, docs/brand-system.md). The brand-surface investment is load-bearing by construction, not optional — a fact that holds regardless of the mt#2046 head-noun decision.
Compound multiplier (1 + 1 = 3). Compounds multiply associations; each constituent brings its own semantic circle and the compound exponentiates them (PowerBook, BlackBerry, Facebook, Windsurf, DreamWorks). Minsky already realizes this at the operand layer — Minsky Mesh, Minsky Cockpit, Minsky Section, Minsky Asks — a deliberate two-tier strategy: the referent (Minsky) above, compounding operands below. New primitives should compound with the locked operands rather than stand alone where a compound would multiply.
Processing fluency for coined primitives. A coined word works when its morphemes are individually familiar (Vercel = ver- truth/verde + -cel accelerate); it fails when abstract-from-engineering reads as opaque (Codium). Coin new primitives from familiar morphemes, not from sophistication.
Three checks before adding a primitive to §7.
- Polarization — does it provoke argument on first hearing? (Comfortable consensus = too safe.)
- Compound — does it multiply with the locked operands / referent (1 + 1 = 3), rather than sit as a lone token?
- Code-coherence — does it carry the Cyberbrain / Section 9 register (§2) and survive the bridge-as-affect heuristic (§3)?
Before any candidate ships it must also pass the prior-use / trademark-collision screen — that screen lives in /name-product and is mandatory (the MINSKY mark itself is contested; see §7a and mt#2046).
Anti-patterns at the naming layer.
- Descriptive primitives (
task-runner, review-bot-manager) — statement not story; forfeits both cumulative and asymmetric advantage.
- Greek/Latin sophistication (the Codium / Anthropic / Anduril shape) — abstract-coined where the substrate is already abstract; violates make-intangible-tangible.
- Single token where a compound would multiply — a lone coinage where Minsky would carry two semantic circles.
- Post-hoc sound-symbolism rationale — retrofitting a phoneme story onto a name chosen for other reasons. This is the Pepsi/Arnell trap (§6) at the naming surface: cite the sound-symbolism first to drive the choice, never to dress up one already made.
7a. Note on the "led by a principal" qualifier (retired 2026-05-31)
Earlier versions of this skill carried the foreground tagline as "The cyberbrain for software organizations led by a principal." The qualifier led by a principal has been retired from the foreground tagline form as of 2026-05-31, on three grounds:
- It conflicts with Eugene's own recursive reframe. Position: Levels of principality (mt#1953, 2026-05-20) is explicit: "The binary distinction in the Principal Substrate paper — principal substrate vs. team substrate — is useful for analytical clarity but misleading as ontology. The two terms name different positions on a spectrum, not different categories." The qualifier presupposes the binary the recursive paper dissolves; "led by a principal" is true at every level of the recursion, which makes appending it to a foreground tagline either tautological (every level has a principal) or misleadingly level-specific (sounds like "single-leader hierarchy" — wrong).
- It's opaque to first-time readers. "Principal" is corpus jargon. Without position-paper context, readers either don't know what it means, interpret it as single-leader hierarchy, or wonder why the qualifier is there.
- It violates the story-over-statement principle. Per the Lexicon Branding analysis (mt#2045 lineage), "Azure starts a story; cloud-pro makes a statement." The bare "The cyberbrain for software organizations" starts a story; appending "led by a principal" constrains it toward a specific (and binary-coded) answer — statement-mode.
What survives intact: the principal-substrate frame as strategic positioning in body copy, position papers, CLAUDE.md §Principal Context, decision-defaults.mdc, and product-design discipline. The recursive paper does not retire "principal" as a concept; it retires the binary as ontology. The Principal vocabulary term remains locked (see row in §7 above). What changes is only the foreground-tagline form: the qualifier is no longer appended to the customer-facing one-liner.
Provisional status. This is a foreground-tagline retirement, not a final tagline decision. The longer-term tagline (and whether it changes again as part of any head-noun decision) is coupled with mt#2046 (Brand-name exploration umbrella — should Minsky be renamed?). Treat the bare "The cyberbrain for software organizations." form as the provisional foreground until mt#2046's verdict lands.
8. Composition with pz-voice — signal vs. channel
pz-voice (mt#1952) is the signal layer: the principal's literary voice, the corpus-grounded substance, the operative-ontology stance applied to whatever subject the writing covers. It carries WHAT is claimed.
This skill (minsky-brand) is the channel layer: the cultural codes, the visual register, the layered references, the bridge-as-affect discipline. It carries HOW the surface feels to the audience.
Together they form the brand identity at two layers:
| Layer | Skill | Surface | Trade-off |
|---|
| Signal | pz-voice | Prose substance (manifesto, position paper, blog post) | Voice without channel reads as a Twitter thread, not a brand artifact. |
| Channel | minsky-brand (this skill) | Visual register (typography, color, layout, imagery) | Channel without signal reads as a stylish but empty cultural-code play. |
Per-surface balance (workshop output, /pz-voice §7):
| Surface | Signal / channel split |
|---|
| Position paper | ~90 / 10 (almost all voice; cultural code is footnote-only) |
| Manifesto / About page | ~70 / 30 (voice-dominant; cultural code in visual frame) |
| Marketing-site copy | ~40 / 60 (voice in section copy; cultural code in visuals, imagery, motion) |
| Visual surfaces (hero, screenshot framing, logo treatment) | ~0 / 100 (cultural code carries; voice is absent at the pixel layer) |
When invoking this skill alongside pz-voice, the balance above tells you which is doing the work for the surface you're authoring. Surfaces that need both — marketing copy, About pages, blog posts — should load both skills.
9. Anti-patterns at the brand-foundation layer
These violate the locked register at the foundation level (distinct from format-level anti-patterns like "centered hero" or "WebGL shader" — those belong to marketing-site-design):
- Literal anime characters, mecha, magical girls, product-name pastiche. Per the bridge-as-affect discipline (§3) — borrow at the layer of register, not at the layer of imagery.
- Iron Man / JARVIS framing. Overdone in Instagram cloud-AI demos; would read as derivative.
- Skynet / Terminator-coded futurism. Wrong cultural code entirely. The brand is operational substrate, not adversarial AI menace.
- Conflating Minsky with "team substrate." Per the Principal Substrate position paper, Minsky's primary frame is principal-substrate (extension of one mind) on a spectrum, not team substrate (coordination for groups). Marketing copy that defaults to "for teams" misses the locked frame.
- Single-reference pastiche. Carrying only one of the five layered references (e.g., a literal GitS pastiche without Iso warmth or Magilumière tonal lock) reads as cosplay. The brand lives in the intersection.
- SaaS hyperbole, exclamation, marketing-affirmation. Belongs to
pz-voice's no-go register; cited here because brand surfaces must compose the two skills.
- Treating the cultural code as decoration. The code carries the proposition. If a layer can be removed without the surface losing meaning, it was decoration, not signal.
10. Upstream sources
- Strategic anchor (the why): Position: Principal substrate vs team substrate (mt#1931). The thesis behind the locked myth and the spectrum-not-binary framing of principal-substrate.
- Operational reference (the how at the implementation layer):
docs/brand-system.md (mt#1932). Concrete tokens: typography stack, color palette (hex + OKLCH), motion budget, vocabulary inventory, WCAG contrast, font licensing, cockpit migration table. Surfaces consume this directly.
- Workshop derivation:
marketing-site-design/references/minsky-myth-2026-05.md. End-to-end walk through Steps 1–5 of the myth-selection workshop, with Minsky as the brand. Use as the worked reference when running this process for any future Minsky-surface or for an adjacent brand.
- Voice substrate:
/pz-voice (mt#1952). The signal layer. Composes per §8 above.
- Adjacent-product analytical methodology:
/analyze-adjacent-product (mt#1944). Peirce-Barthes-Oswald semiotic framework, Pepsi/Arnell discipline, bridge-as-affect, per-analysis capture workflow. Use when reading a competitor's surface to inform Minsky positioning decisions.
- Principal corpus: mt#1930. Query via
mcp__minsky__principal_corpus_search / principal_corpus_similar; synthesized memeplex via mcp__minsky__memory_search with tag principal-thinking.
11. Surface skills that depend on this foundation
| Skill | Surface | What it adds on top of this foundation |
|---|
/marketing-site-design | Marketing site, microsites, launch pages, position-paper landing pages | Idiom selection (B for product-screenshot-dominant), marketing-specific layout patterns (left-caption + right-product hero, alternating sections, co-product logo strategy), workshop process for new surfaces, marketing-format anti-patterns, vendored Tier-1 skill bundle. |
/cockpit-design | Cockpit web app (src/cockpit/web/**) | Minsky-domain entity model (tasks/sessions/changesets/PRs/asks/agents), mission-control density patterns, command-palette UX, drill-down navigation, attention-debt visualization, workstream display. Cockpit's mission-control register is one organ inside the cyberbrain frame, not an independent design language — this foundation governs both. |
Future Minsky-surface skills (talk-deck-design, social-post-design, etc.) should reference this skill as their strategic anchor in the same pattern.
Reference use and trademarks
The cited franchises and works (Ghost in the Shell, Stand Alone Complex, Neon Genesis Evangelion, Mitsuo Iso's Orbital Children and Dennō Coil, Magilumière Magical Girls Inc., Stross's Accelerando, and others) are referenced nominatively for cultural-code recognition only. No affiliation, sponsorship, or endorsement is claimed. All trademarks belong to their respective owners. Surface implementations must follow the bridge-as-affect discipline in §3 — atmospheric register, never literal depiction.
Cross-references
/marketing-site-design — surface skill for marketing-site work; depends on this foundation./cockpit-design — surface skill for cockpit work; depends on this foundation./pz-voice — signal layer; composes with this foundation per §8./analyze-adjacent-product — analytical methodology for reading adjacent brands. The Pepsi/Arnell discussion (§2) and bridge-as-affect framework (§3) referenced from this skill live there.docs/brand-system.md — operational reference for surface implementations.- CLAUDE.md
§Principal Context — Minsky's commercial-product framing.
- CLAUDE.md
§Documentation Taxonomy — the strategic / operational / agent-consumable tier model that places this skill in its slot.
- Notion strategic anchors:
- Source texts (Minsky brand register):
- Charles Stross, Accelerando (2005) — Manfred Macx and the flock
- Ghost in the Shell: Stand Alone Complex (Production I.G., 2002–2005) — Section 9, Tachikomas, Stand Alone Complex concept
- Neon Genesis Evangelion (Anno / Gainax, 1995–1996) — Magi, NERV, sync ratio, density-with-soul
- Mitsuo Iso, Dennō Coil (2007) and Orbital Children (2022) — AR/AI/companion warmth
- Magilumière Magical Girls, Inc. (Magilumière Co. Ltd., 2024 manga/anime) — magick-as-corporate-profession tonal lock
- Originating tasks:
- mt#1927 — installed the marketing-site-design bundle with the foundation absorbed inline
- mt#1929 — umbrella; this is child #4 (Phase 2 of the brand workstream)
- mt#1931 — Principal Substrate position paper
- mt#1932 — operational brand-system reference (
docs/brand-system.md)
- mt#1933 — this skill (extracted the foundation from marketing-site-design)
- mt#1944 — extracted analyze-adjacent-product analytical methodology
- mt#1952 — pz-voice skill
