THE ARCHETYPE

Status / authority: Legacy-derived detailed source; Archetype remains current, and this document supplies compatible detail under the current Legant Method Reference
Effective date: 2026-05-23; current-use boundary revised 2026-08-05
Dependencies: ../LEGANT_METHOD_REFERENCE.md; current person-model evidence; frozen ARC release
Supersedes: ARC Archetype Discovery Protocol (2).md historically. Current-use repairs supersede this file's former Focus Line dependency without changing issued historical artifacts.

Current-use notice: Preserve this source for the conceptual development of Archetype and for historical interpretation. For new work, use the current Legant Method Reference. Archetype is a compression of the working person-model; it does not require a Focus Line or Four Narrative Constraints artifact.

Version 3 (2026-05-23). Supersedes ARC Archetype Discovery Protocol (2).md.

This document defines what the archetype is, what it does, where it fits in the legacy ARC structure, what makes a good one, and why it matters. The private production procedure for applying these concepts is maintained separately and is not part of this client-readable source.

What an archetype is

The archetype is the noun-ification of the most valuable transformation a person contributes — the pivotal move that bridges their Violation and their Vision, compressed into a single portable handle.

Form. One word; two at most. Verb-derived noun (Decoder, Renderer, Weaver) or a metaphorical noun where the role inherently names the mechanism (Forgemaster forges; Showrunner runs; Producer produces). The handle must encode the mechanism with no decorative parts. If one word, the noun alone conveys what the person does. If two words, both words do real work — neither decorative (Override Orchestrator passes because Override names what gets designed and Orchestrator names how it gets executed; Professor Exito fails because Professor encodes pedagogy, not the underlying decoding mechanism). The test applies to the full handle, not just the head noun.

Inputs it compresses. The archetype is named after the analytical work, not in parallel to it. By the time an archetype is on the table, the current person-model should be good enough to proceed: the recurring transformation and Verb are supported across the record, and relevant Violation, Vision, Core Tension, and counterevidence have helped specify the mechanism. The archetype does not re-discover that work. It compresses it. This does not make the model final truth; it makes the current hypothesis stable enough to test in the next artifact.

Examples:

Decoder (method-owner example) — one who decodes wiring patterns and renders them as operable systems
Override Orchestrator (anonymized client example) — one who designs strategic overrides and coordinates their execution

What an archetype does

The archetype does three jobs at once.

1. Compresses the working person-model into a portable name that survives deepening internal detail. The source-grounded model, and eventually the Operating Manual, Positioning Report, and Microscript Bank, carry the full analytical depth. The archetype is a candidate persistent label across that deepening. New material should attach to the same name when the name keeps earning its place. If later evidence shows the handle is wrong, it changes. A single word is doing the work of carrying everything underneath, but only while it remains the best compression.

2. Replaces less aligned identities. People walk into the work carrying self-descriptions that function as identities but don't fit the wiring. One client described surface-level creative outputs rather than the deeper contribution pattern. The archetype functions as an identity-replacement. The standard isn't captures every dimension of who they are. The standard is truer than what they walked in with, and tight enough they can use it. Less aligned out, more aligned in.

3. Minimizes the disconnect between internal depth and external read. No outsider hearing the archetype will understand it as deeply as the person does. They don't have access to the V-V-V analysis, the accepted verb, or the lived chapters that built it. That's not what the archetype is trying to do. The goal is for the external read to be close enough to true that the listener doesn't form a wrong picture. A decent first-understanding, not a complete one. The archetype's job is to make the wrong picture less likely, not to communicate the full wiring.

Where the archetype fits in Innate Edge

The archetype sits downstream of analysis, upstream of deliverables.

Upstream of the archetype — the analytical work that produces the inputs:

The recurring transformation and current best Verb, supported across chapters
Relevant Violation, Vision, or Core Tension evidence where it helps specify the mechanism
Counterexamples, competing handles, and evidence the model does not explain

Downstream of the archetype — the operational deliverables that the archetype anchors:

Operating Manual (identity anchor — "I am a [archetype]")
Positioning work (Microscript Bank tested against the archetype noun)
Field Guide (extended-metaphor application)
The client's own use — self-talk, decision filter, public-facing language

The archetype is the compression layer between the analytical work and the external/operational deliverables. It is downstream-of-analysis because if the analysis is not yet good enough to proceed, the archetype is naming a moving target. It is upstream-of-deliverables because the deliverables refer to it. Later friction can still force the analysis, the archetype, or both to evolve.

Two states: Triage and Adoption

The archetype has two states.

Triage is the analytical compression. It runs after the person-model and Verb are good enough to proceed and produces one to three workshop candidates with rationale. It does not require a Focus Line or a completed direction artifact. Triage output goes into the Decode artifact as workshop options.

Adoption is the formal identity anchor. It follows only when the client recognizes the archetype as truer than what they walked in with, can explain or correct the mechanism in their own words, and begins using it naturally. Adoption anchors the Operating Manual identity, the Positioning Microscript Bank, and downstream deliverables.

Adoption is not auto-cascading from Triage. Some archetypes emerge quickly and adoption follows Triage immediately. Others require extended incubation, where the client lives with candidates for weeks before resonance lands. Treat the gap as a feature, not a bug — it lets the client respond to candidates before committing.

Resonance and adoption are not proof that the handle is valid. Before adoption, record what the candidate predicts about recurring behavior, where its jurisdiction ends, and what future evidence would narrow, rename, or retire it. Later friction should be checked against those prospective conditions rather than explained away after the fact.

What makes a good archetype

These are conceptual criteria. The private production procedure applies them through tests and gates.

Mechanism Fit (the gate). The handle encodes the mechanism with no decorative parts. The test applies to the full handle, not just the head noun. Single-word: the noun alone conveys the mechanism (Decoder, Surfacer, Weaver). Two-word: both words do real work, neither decorative (Override Orchestrator ✓; Edge Cartographer ✓ when Edge names a real entry pattern; Professor Exito ✗ because Professor is decorative — it encodes pedagogy, not the mechanism). If a candidate fails the test, the archetype isn't compressing the wiring — it's decorating it.

Biographical resonance. The mechanism named by the archetype is already established as something the person reliably runs. This is usually inherited from the Verb work — by the time the Verb is good enough to proceed, the cross-chapter coverage has been tested. The archetype doesn't re-prove it. It names it.

External legibility. A first-time listener can form a decent picture from the name plus a one-sentence frame. The standard is decent, not complete.

Simplicity. One word ideally; two when the Verb's structure requires it. Length follows from mechanism fit, never the reverse. If a second word isn't doing real work, cut it.

Distinctive. Not corporate-bland. Not a generic verb-noun (Catalyst, Operator, Strategist, Builder) unless the person has exceptional evidence of ownership of that category. Generic-sounding archetypes can survive when they're specifically owned — the method owner uses "Decoder" because he built the decoding methodology — but the bar is high.

Why it matters

Without an archetype, the working model stays internal. A person can understand it deeply and still have no way to introduce that depth without a thirty-minute explanation. The archetype makes the internal clarity transmittable. It does not transmit the whole thing. It transmits enough that the listener is less likely to form the wrong picture.