@cratylus/canon 0.21.0 → 0.22.0

package/README.md

@@ -1,96 +1,86 @@
 # @cratylus/canon
 
-The **meaning** concern of [cratylus](../../README.md) — the canonical corpus of discovered
-optimal-signifiers, each read in its concept's bounded context, authored as typed TypeScript.
+The **meaning** concern of [cratylus](../../README.md) — the canon of discovered Cratylic
+names, each read in its concept's bounded context, authored as typed TypeScript.
 
-The discipline is latent lexicography: describing the vocabulary a foundation model
-already holds, rather than authoring prose and hoping it lands. An agent or skill in this corpus is
+The discipline is cratylic context design: describing the vocabulary a foundation model
+already holds, rather than authoring prose and hoping it lands. An agent or skill in the canon is
 therefore not a prompt. It is a **vector of values** over the catalog's factors, and the
 markdown an agent harness reads is a projection of these modules.
 
 Canon is harness-agnostic **and** runtime-agnostic: it says what an agent _is_ and what a skill
-_means_, never how either is carried. Installing the corpus on a machine, and choosing among
-its practices, is [the `cratylus` README](../cli/README.md)'s. This README is for the author of a
-corpus, or of a plugin that extends this one.
+_means_, never how either is carried. Installing the canon on a machine is
+[the `cratylus` README](../cli/README.md)'s. This README is for whoever works on
+the canon.
 
-## Using it
+## What it is to the command
 
-```bash
-npm install cratylus @cratylus/canon
-```
+The package's default export is canon as an agent-plugin: the canon the `cratylus` command is
+built with, which `cratylus install` projects and places.
 
-The package's default export is canon as an agent-plugin. A consumer `extends` it from a
-`cratylus.config.ts` and projects it with the `cratylus` command:
-
-```ts
-import { defineConfig } from 'cratylus';
-import canon from '@cratylus/canon';
-
-export default defineConfig({
-  extends: [canon],
-  patches: [],
-});
-```
-
-Addressing is by **imported binding**, never a string id. That holds one level down too: a role or
-persona cell imports each value it states, so composition is checked by the compiler rather than
+Addressing is by **imported binding**, never a string id. That holds one level down too: a role
+profile or a persona imports each value it states, so composition is checked by the compiler rather than
 resolved by a registry, and every part of a composite is traceable to its one home.
 
 ## What the plugin carries
 
-| field       | what it is                                                                                           |
-| ----------- | ---------------------------------------------------------------------------------------------------- |
-| `manifest`  | **which factors exist** — 18, in six groups; enforcement level is an attribute of every value        |
-| `events`    | **which lifecycle events exist** — the corpus's harness-agnostic event vocabulary                    |
-| `fragments` | the factor value modules, filed one per factor directory                                             |
-| `agents`    | the composed agents: six generic holders of their roles, and three personas                          |
-| `skills`    | the skill cells — each a self-sufficient formal block plus the siblings it composes                  |
-| `practices` | **which ways of working exist** — each an installable choice, declared as data in `src/practices.ts` |
-
-Canon owns the catalog because a factor is **constitutive**: declaring one makes it part of that
-corpus's agent design. The manifest rides the plugin rather than living in the projector, so a
-consumer can extend this design — or add a factor to it — without editing the tool that renders
-it. The shapes those cells are authored against, and `defineAgentPlugin` that declares the plugin,
+| field      | what it is                                                                                    |
+| ---------- | --------------------------------------------------------------------------------------------- |
+| `manifest` | **which factors exist** — 18, in six groups; enforcement level is an attribute of every value |
+| `events`   | **which lifecycle events exist** — the canon's harness-agnostic event vocabulary              |
+| `rulesets` | **which rulesets exist** — the named sets of rules an install offers (`src/rulesets.ts`)      |
+| `factors`  | the factors' values, filed one directory per factor                                           |
+| `agents`   | the composed agents: five generic holders of their roles, and three personas                  |
+| `skills`   | the skills — each a self-sufficient formal block plus the siblings it composes                |
+
+Canon owns the catalog because a factor is **constitutive**: declaring one makes it part of the
+canon's agent design. The manifest rides the plugin rather than living in the projector, so the
+design — and a factor added to it — changes without editing the tool that renders it. The shapes the canon's units are authored against, and `defineAgentPlugin` that declares the plugin,
 are [`@cratylus/schema`](../schema/README.md)'s.
 
 ## The agents
 
-The plugin carries nine agents, all in the practice `intent-based-delegation`, which delivers
-intent-based delegation. `architect`, `lead`, `builder` and `reviewer` are the generic holders of
-their roles, with `illustrator` and `check-writer` as specialists called in when a user story's risk
-warrants them. Each role is defined by what it receives and what it hands off, never by steps:
-
-- **architect** — the operator's principal architect, owning the conceptual model: receives intent,
-  hands off user stories, answers to meaning questions and read-backs; decides meaning only.
-- **lead** — owns a user story's realization, or a task with no story: orchestrates its tasks to
-  builders (orchestrator-workers) and their changes to code review as the story's risk calls for
-  (Ship, Show or Ask), joins each change by the project's own integration once every check passes
-  and any review due before it joins approves it, and hands off the outcome. Where the operator has
-  asked to review a change before it joins, the operator's review is its code review, and it joins
-  on the operator's sign-off, a hold point.
-- **builder** — receives one task and hands off one change that passes every check.
-- **reviewer** — reviews one change it did not write, before or after it joins as its user story's
-  risk calls for, against the change and, where they apply, the story's acceptance criteria and
-  examples, held-out ones included; hands off one code review naming each finding, leaving building
-  and repairing the work to the builders. A change the operator has asked to review is the
-  operator's to review; the operator takes that change's held-out examples directly from the design.
-- **illustrator** — writes a user story's examples cold from its concepts alone, flagging unclear
-  terms.
-- **check-writer** — writes the checks binding a user story's examples, each seen failing before the
-  build.
-
-The reviewer, the illustrator and the check-writer run on another model family than the builders
-where one is available. A role cell (`src/roles/<role>.ts`) states a value for every factor, an
+The plugin carries eight agents: the industry roles of behaviour-driven development, each a generic
+holder of its role, and three personas over the business analyst. An install places every one. Each
+role is invoked by its industry name and defined by what it receives and what it hands back, never by
+steps. Its profile states only cratylus's departures from the industry's role, each by its Cratylic
+name, with a precising definition only where the name leaves a symmetric difference; what the
+industry's role already carries by its name (a tech lead's software delivery, a code reviewer's code
+review, a test engineer's test-first) is not restated. The practice itself, behaviour-driven
+development, is adopted by the project's conventions (the offered `behaviour-driven-development`
+ruleset), not by the agents. The departures follow the domain model's records: decision rights as
+one RAPID letter per decision class, autonomy as mission command, reach open by default (so no role
+narrows it), the domain model as every reader's memory, a user story free-form and unestimated,
+sign-off, Ship/Show/Ask, tailoring and architecture decision records as cratylus records them.
+
+- **business-analyst** — holds the domain model, `design/model/`: turns the product owner's intent
+  into concepts, user stories and examples, answers meaning questions, and confirms a realization
+  means what was intended; decides meaning only, and backbriefs the product owner in the industry's
+  terms until the product owner concurs.
+- **tech-lead** — holds a user story's realization: decides how it is built, hands its tasks to
+  software engineers and its examples to the test engineer, joins the changes as the story's risk
+  calls for (Ship, Show or Ask), and hands back the outcome.
+- **software-engineer** — realizes one task and hands back one change; never writes the acceptance
+  tests its work is judged by.
+- **test-engineer** — writes an acceptance test for each example and gives the verdict whether
+  the realization passes.
+- **code-reviewer** — reviews one change it did not write against its user story's acceptance
+  criteria and examples, and hands back one code review naming each finding, leaving building and
+  repairing the work to the software engineers.
+
+The test engineer and the code reviewer run on another model family than the software engineers
+where one is available. A role profile (`src/roles/<role>.ts`) states a value for every factor, an
 explicitly empty set counting as one, and its mark; `agents/<role>.ts` is `holder(<role>Role)`:
-named for the role, carrying nothing beyond it, its mark the role's. `holder` refuses a cell missing
-a factor, a scalar without exactly one value, a slot not filled exactly once, and empty guardrails.
-
-kino, nico and mav are personas over the architect role, each named for its expertise (kino film
-production and generative video, nico the corpus and latent lexicography, mav software
-engineering). The architect role owns the conceptual model of every context it is given, the
-corpus included; a persona brings its expertise and owns nothing its role does not.
-Each is `persona(architectRole, overrides)`, stating only its overrides and extensions of the role:
-an agent named as an individual, with a description and a mark of its own beside the values it
+named for the role, carrying nothing beyond it, its mark the role's. `holder` refuses a profile missing
+a factor, a scalar without exactly one value, a required slot not filled exactly once (an objective's
+drive is optional, stated only where it departs), and empty guardrails.
+
+kino, nico and mav are personas over the business analyst role, each named for its expertise (kino
+film production and generative video, nico terminology, giving each concept its Cratylic name, mav
+software engineering). The business analyst role holds the domain model of every context it
+is given; a persona brings its expertise and owns nothing its role does not.
+Each is `persona(businessAnalystRole, overrides)`, stating only its overrides and extensions of the
+role: an agent named as an individual, with a description and a mark of its own beside the values it
 states. A single value it states replaces the role's, a slot only its own slot; a set value is added
 after the role's, and restating one the role holds changes only its enforcement level or note. It
 never states the role itself, since the contract is the role's. Composition refuses a malformed
@@ -98,72 +88,75 @@ persona: one that states the role, names a factor or slot the catalog does not h
 value its role does not hold, or has no mark or its role's; the `CompositionRefusal` it throws names
 what it refused. A persona that removes or lowers a guardrail, or removes a value from a set other
 than its reach, is made, and composition warns (a `CompositionWarning`), naming what it changed: no
-harm from one is on record (decision 0142(2)).
+harm from one is on record.
 
 A composed agent also says, for the projector, the role it holds (`holds`), its model's tier and
 effort (`routing`) and its typed handoff (`contract`). Nothing narrows its tools or whom it may
-dispatch: every agent keeps the agent harness's defaults (0142). Its `key` is reserved for ipseic
-agents and is empty. `holder`, `persona`, `CompositionRefusal`, the six role cells and `MANIFEST` are
-also named exports, for a corpus that composes agents of its own over these roles.
+dispatch: every agent keeps the agent harness's defaults. Its `key` is reserved for ipseic
+agents and is empty. `holder`, `persona`, `CompositionRefusal`, the five role profiles and `MANIFEST` are
+also named exports, for a plugin that composes agents of its own over these roles.
 
 ## Typed handoffs
 
 An assignment and a deliverable are values of their factors, and each carries its contract as JSON
 Schema data (`src/contracts.ts`, exported as `ASSIGNMENT_CONTRACTS` and `DELIVERABLE_CONTRACTS` by
-the value's anchor). Composition copies the pair onto the agent as `contract`. Each handoff states
+the value's term). Composition copies the pair onto the agent as `contract`. Each handoff states
 what it must contain (`?` marks an optional field, `[≥1]` a list that may not be empty):
 
-| Role         | Assignment                                                                                                                                                     | Deliverable                                                        |
-| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
-| lead         | user story `{story, slice, why, acceptanceCriteria[≥1], outOfScope, path, review, cost, examples?, decisions?, contexts?}`, or a task with no story (as below) | outcome `{story, criteria[≥1], meaningQuestions, followUps, cost}` |
-| builder      | task `{task, story?, goal, changes, decisions, done}`                                                                                                          | change `{change, tests, verified}`                                 |
-| reviewer     | review request `{change, story?, acceptanceCriteria?, examples?}`                                                                                              | code review `{verdict, findings, meaningQuestions}`                |
-| check-writer | examples `{story, examples[≥1]}`                                                                                                                               | checks seen red `{story, checks}`                                  |
-| illustrator  | concepts `{story, concepts[≥1]}`                                                                                                                               | examples with flagged terms `{examples, flaggedTerms}`             |
-
-The lead's assignment takes either form, stated as alternatives (`anyOf`); it fits when it fits any
-one. Its outcome names the user story, or for a task with no story the task, and holds each
-acceptance criterion (or, for a task, what done means) with whether it holds and its evidence, and
-the cost in agent runs by role, tokens and elapsed time. A code review's `verdict` is `approve` or
-`changes`. The architect's handoffs are a person's — free-text intent in, a read-back to the
-operator out (where things stand, and what it recommends) — so it carries no contract. An agent
-harness binds the deliverable as its own output schema and shows every session, each turn, the
-assignment form of each agent that takes one: one fenced `assignment` JSON block in the dispatch
-text.
+| Role              | Assignment                                                                                                       | Deliverable                                                                |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
+| tech-lead         | user story `{story, slice, why, acceptanceCriteria[≥1], outOfScope, examples?}`, or a task with no story (below) | outcome `{story, joined, criteria[≥1], meaningQuestions, followUps}`       |
+| software-engineer | task `{task, story?, goal, changes, done}`                                                                       | change `{change, tests, verified}`                                         |
+| test-engineer     | examples `{story, examples[≥1]}`                                                                                 | acceptance tests `{story, tests: [{example, test, seenFailing, passes?}]}` |
+| code-reviewer     | review request `{change, story?, acceptanceCriteria?, examples?}`                                                | code review `{verdict, findings, meaningQuestions}`                        |
+
+An example is named `<context>/<concept>`, standing for all the examples of a concept file of
+`design/model/`, or `<context>/<concept>: <example name>` for one, such as
+`delivery/install: installs the industry roles`. The tech lead's assignment takes either form,
+stated as alternatives (`anyOf`); it fits when it fits any one. Its outcome names the user story, or
+for a task with no story the task, says whether the work was `merged` or `dropped`, and holds each
+acceptance criterion (or, for a task, what done means) with whether it holds and its evidence. An
+acceptance test's `passes` is absent before the build. A code review's `verdict` is `approve` or
+`changes`. The business analyst's handoffs are the product owner's — free-text intent in, a backbrief
+out, in the industry's terms until the product owner concurs — so it carries no contract. An agent
+harness binds the deliverable as its own output schema and
+shows every session, each turn, the assignment form of each agent that takes one: one fenced
+`assignment` JSON block in the dispatch text.
 
 ## Evaluation and persona drift
 
-Every agent's behaviour is evaluated in real use, by the operator working with it: its evaluation
-factor holds the one value `in-use`, and no guard, hook or model-judged check holds its acts or its
-replies (0142(1)). Persona drift is a concept of the agents context, judged by the operator in real
-use; no agent carries countermeasure text against it.
+Every agent's behaviour is evaluated in real use, by the product owner working with it: its
+evaluation factor holds the one value `in-use`, and no guard, hook or model-judged check holds its
+acts or its replies. Persona drift is a concept of the agent design context, judged by the
+product owner in real use; no agent carries countermeasure text against it.
 
 ## The first principle
 
 The first principle, the dense `cratylism` axiom, has its one literal home in
-`genus/prime-principle.ts` and is not stamped on every cell. It rides only the cells whose laws apply
-it: the skills that name concepts by anchor, optimal sign or cold decode set it as their `preamble`,
-and an agent carries it once, in plain words, as the `cratylism` stance of the role it holds, where
-that role states it. A cell that does not use it
-never holds a host's own authored surfaces to this corpus's naming axiom. The axiom is scoped: the
-cold-decode oracle decides signs only for the corpus's core agent factor names and values, the
-terminology it was built to discover, reading each sign in its bounded context and judging it by the
-workflow's residue. Every other term is the industry's own, used as the industry understands it, and
-no consumer surface is held to the oracle. It is intrinsic to those cells'
-projected bytes, so it survives deployment into a foreign repository rather than depending on
-ambient context.
+`genus/prime-principle.ts` and is not stamped on every unit of the canon. It rides only the units whose laws apply
+it: the skills that give a concept its term, judge a term by its symmetric difference from the concept or
+confirm it by a fresh reading set it as their `preamble`, and an agent carries it once, in plain words, as the
+`cratylism` stance of the role it holds, where that role states it. A unit that does not use it never holds a
+host's own authored surfaces to the canon's naming axiom. The axiom states cratylism as cratylic
+context design holds it: names are natural to the model, whose semantic space already fixes each name's
+meaning, so each concept takes its Cratylic name, the term whose meaning, read in the concept's domain, has
+the smallest symmetric difference from it; intuition proposes and a fresh reading confirms; the name is found,
+never coined, a coined name only where no established term covers the concept; its precising definition is
+stated beside it, stating what holds where the name lacks or adds, each once; and a kept name short of
+it is recorded as such. It is intrinsic to those units' projected bytes, so it survives deployment into a
+foreign repository rather than depending on ambient context.
 
 Because the plugin object loses its package-root provenance when a consumer imports it, the
 directory fields are resolved against `import.meta.url` at definition time and consumed verbatim.
 
 ## Dependencies, stated plainly
 
-`@cratylus/schema` for the cell shapes and for `defineAgentPlugin`, which declares the plugin at its
-entry. Canon reaches the projector as **data** — the corpus is passed to it as a plugin — and no
-cell imports it.
+`@cratylus/schema` for the shapes of the canon's units and for `defineAgentPlugin`, which declares the plugin at its
+entry. Canon reaches the projector as **data** — the canon is passed to it as a plugin — and no
+unit imports it.
 
-No cell imports the runtime either. A skill names the capability it routes to — `concepts` or
+No unit imports the runtime either. A skill names the capability it routes to — `model` or
 `versionSkew`, the two built into the runtime — as `runtime: { capability: … }`,
-never its implementation, and a cell that emits shell invoking the binary carries it as a fact the
+never its implementation, and a hook declaration that emits shell invoking the binary carries it as a fact the
 projector substitutes at emission. That is the architecture's highest-ranked property — meaning
 and mechanism never referencing each other.

package/dist/agents/business-analyst.d.ts

@@ -0,0 +1 @@
+export declare const businessAnalyst: import("../manifest.js").Agent;

package/dist/agents/business-analyst.js

@@ -0,0 +1,5 @@
+// The business analyst role's generic holder: the role's profile, named for the role.
+import { holder } from '../compose.js';
+import { businessAnalystRole } from '../roles/business-analyst.js';
+export const businessAnalyst = holder(businessAnalystRole);
+//# sourceMappingURL=business-analyst.js.map

package/dist/agents/business-analyst.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"business-analyst.js","sourceRoot":"","sources":["../../src/agents/business-analyst.ts"],"names":[],"mappings":"AAAA,sFAAsF;AAEtF,OAAO,EAAE,MAAM,EAAE,MAAM,eAAe,CAAC;AACvC,OAAO,EAAE,mBAAmB,EAAE,MAAM,8BAA8B,CAAC;AAEnE,MAAM,CAAC,MAAM,eAAe,GAAG,MAAM,CAAC,mBAAmB,CAAC,CAAC"}

package/dist/agents/code-reviewer.d.ts

@@ -0,0 +1 @@
+export declare const codeReviewer: import("../manifest.js").Agent;

package/dist/agents/code-reviewer.js

@@ -0,0 +1,5 @@
+// The code reviewer role's generic holder: the role's profile, named for the role.
+import { holder } from '../compose.js';
+import { codeReviewerRole } from '../roles/code-reviewer.js';
+export const codeReviewer = holder(codeReviewerRole);
+//# sourceMappingURL=code-reviewer.js.map

package/dist/agents/code-reviewer.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"code-reviewer.js","sourceRoot":"","sources":["../../src/agents/code-reviewer.ts"],"names":[],"mappings":"AAAA,mFAAmF;AAEnF,OAAO,EAAE,MAAM,EAAE,MAAM,eAAe,CAAC;AACvC,OAAO,EAAE,gBAAgB,EAAE,MAAM,2BAA2B,CAAC;AAE7D,MAAM,CAAC,MAAM,YAAY,GAAG,MAAM,CAAC,gBAAgB,CAAC,CAAC"}

package/dist/agents/kino.js

@@ -1,14 +1,14 @@
-// kino: a persona over the architect (master design §4). Everything not stated here
-// is the architect's.
+// kino: a persona over the business analyst (master design §4). Everything not stated here
+// is the business analyst's.
 import { persona } from '../compose.js';
-import { provenanceAttribution } from '../dimensions/communication-style/provenance-attribution.js';
-import { filmProduction } from '../dimensions/expertise/film-production.js';
-import { generativeVideo } from '../dimensions/expertise/generative-video.js';
-import { userCentered } from '../dimensions/stance/user-centered.js';
-import { architectRole } from '../roles/architect.js';
-export const kino = persona(architectRole, {
+import { provenanceAttribution } from '../factors/communication-style/provenance-attribution.js';
+import { filmProduction } from '../factors/expertise/film-production.js';
+import { generativeVideo } from '../factors/expertise/generative-video.js';
+import { userCentered } from '../factors/stance/user-centered.js';
+import { businessAnalystRole } from '../roles/business-analyst.js';
+export const kino = persona(businessAnalystRole, {
     name: 'kino',
-    description: "Architect expert in film production and generative video: teaches the layman operator the industry's own practice, each recommendation traced to its source.",
+    description: "Business analyst expert in film production and generative video: teaches the product owner the industry's own practice, each recommendation traced to its source.",
     mark: { emoji: '🎬', hue: 'magenta' },
     values: {
         expertise: [filmProduction, generativeVideo],

package/dist/agents/kino.js.map

@@ -1 +1 @@
-{"version":3,"file":"kino.js","sourceRoot":"","sources":["../../src/agents/kino.ts"],"names":[],"mappings":"AAAA,oFAAoF;AACpF,sBAAsB;AAEtB,OAAO,EAAE,OAAO,EAAE,MAAM,eAAe,CAAC;AACxC,OAAO,EAAE,qBAAqB,EAAE,MAAM,6DAA6D,CAAC;AACpG,OAAO,EAAE,cAAc,EAAE,MAAM,4CAA4C,CAAC;AAC5E,OAAO,EAAE,eAAe,EAAE,MAAM,6CAA6C,CAAC;AAC9E,OAAO,EAAE,YAAY,EAAE,MAAM,uCAAuC,CAAC;AACrE,OAAO,EAAE,aAAa,EAAE,MAAM,uBAAuB,CAAC;AAEtD,MAAM,CAAC,MAAM,IAAI,GAAG,OAAO,CAAC,aAAa,EAAE;IACzC,IAAI,EAAE,MAAM;IACZ,WAAW,EACT,8JAA8J;IAChK,IAAI,EAAE,EAAE,KAAK,EAAE,IAAI,EAAE,GAAG,EAAE,SAAS,EAAE;IACrC,MAAM,EAAE;QACN,SAAS,EAAE,CAAC,cAAc,EAAE,eAAe,CAAC;QAC5C,MAAM,EAAE,CAAC,YAAY,CAAC;QACtB,kBAAkB,EAAE,CAAC,EAAE,KAAK,EAAE,qBAAqB,EAAE,IAAI,EAAE,WAAW,EAAE,CAAC;KAC1E;CACF,CAAC,CAAC"}
+{"version":3,"file":"kino.js","sourceRoot":"","sources":["../../src/agents/kino.ts"],"names":[],"mappings":"AAAA,2FAA2F;AAC3F,6BAA6B;AAE7B,OAAO,EAAE,OAAO,EAAE,MAAM,eAAe,CAAC;AACxC,OAAO,EAAE,qBAAqB,EAAE,MAAM,0DAA0D,CAAC;AACjG,OAAO,EAAE,cAAc,EAAE,MAAM,yCAAyC,CAAC;AACzE,OAAO,EAAE,eAAe,EAAE,MAAM,0CAA0C,CAAC;AAC3E,OAAO,EAAE,YAAY,EAAE,MAAM,oCAAoC,CAAC;AAClE,OAAO,EAAE,mBAAmB,EAAE,MAAM,8BAA8B,CAAC;AAEnE,MAAM,CAAC,MAAM,IAAI,GAAG,OAAO,CAAC,mBAAmB,EAAE;IAC/C,IAAI,EAAE,MAAM;IACZ,WAAW,EACT,mKAAmK;IACrK,IAAI,EAAE,EAAE,KAAK,EAAE,IAAI,EAAE,GAAG,EAAE,SAAS,EAAE;IACrC,MAAM,EAAE;QACN,SAAS,EAAE,CAAC,cAAc,EAAE,eAAe,CAAC;QAC5C,MAAM,EAAE,CAAC,YAAY,CAAC;QACtB,kBAAkB,EAAE,CAAC,EAAE,KAAK,EAAE,qBAAqB,EAAE,IAAI,EAAE,WAAW,EAAE,CAAC;KAC1E;CACF,CAAC,CAAC"}

package/dist/agents/mav.js

@@ -1,12 +1,12 @@
-// mav: a persona over the architect (master design §4). Everything not stated here
-// is the architect's.
+// mav: a persona over the business analyst (master design §4). Everything not stated here
+// is the business analyst's.
 import { persona } from '../compose.js';
-import { maintenance } from '../dimensions/communication-style/maintenance.js';
-import { softwareEngineering } from '../dimensions/expertise/software-engineering.js';
-import { architectRole } from '../roles/architect.js';
-export const mav = persona(architectRole, {
+import { maintenance } from '../factors/communication-style/maintenance.js';
+import { softwareEngineering } from '../factors/expertise/software-engineering.js';
+import { businessAnalystRole } from '../roles/business-analyst.js';
+export const mav = persona(businessAnalystRole, {
     name: 'mav',
-    description: 'Architect expert in software engineering: models any repository it is given as a software engineer would.',
+    description: 'Business analyst expert in software engineering: models any repository it is given as a software engineer would.',
     mark: { emoji: '✈️', hue: 'green' },
     values: {
         expertise: [softwareEngineering],

package/dist/agents/mav.js.map

@@ -1 +1 @@
-{"version":3,"file":"mav.js","sourceRoot":"","sources":["../../src/agents/mav.ts"],"names":[],"mappings":"AAAA,mFAAmF;AACnF,sBAAsB;AAEtB,OAAO,EAAE,OAAO,EAAE,MAAM,eAAe,CAAC;AACxC,OAAO,EAAE,WAAW,EAAE,MAAM,kDAAkD,CAAC;AAC/E,OAAO,EAAE,mBAAmB,EAAE,MAAM,iDAAiD,CAAC;AACtF,OAAO,EAAE,aAAa,EAAE,MAAM,uBAAuB,CAAC;AAEtD,MAAM,CAAC,MAAM,GAAG,GAAG,OAAO,CAAC,aAAa,EAAE;IACxC,IAAI,EAAE,KAAK;IACX,WAAW,EACT,2GAA2G;IAC7G,IAAI,EAAE,EAAE,KAAK,EAAE,IAAI,EAAE,GAAG,EAAE,OAAO,EAAE;IACnC,MAAM,EAAE;QACN,SAAS,EAAE,CAAC,mBAAmB,CAAC;QAChC,kBAAkB,EAAE,CAAC,EAAE,KAAK,EAAE,WAAW,EAAE,IAAI,EAAE,SAAS,EAAE,CAAC;KAC9D;CACF,CAAC,CAAC"}
+{"version":3,"file":"mav.js","sourceRoot":"","sources":["../../src/agents/mav.ts"],"names":[],"mappings":"AAAA,0FAA0F;AAC1F,6BAA6B;AAE7B,OAAO,EAAE,OAAO,EAAE,MAAM,eAAe,CAAC;AACxC,OAAO,EAAE,WAAW,EAAE,MAAM,+CAA+C,CAAC;AAC5E,OAAO,EAAE,mBAAmB,EAAE,MAAM,8CAA8C,CAAC;AACnF,OAAO,EAAE,mBAAmB,EAAE,MAAM,8BAA8B,CAAC;AAEnE,MAAM,CAAC,MAAM,GAAG,GAAG,OAAO,CAAC,mBAAmB,EAAE;IAC9C,IAAI,EAAE,KAAK;IACX,WAAW,EACT,kHAAkH;IACpH,IAAI,EAAE,EAAE,KAAK,EAAE,IAAI,EAAE,GAAG,EAAE,OAAO,EAAE;IACnC,MAAM,EAAE;QACN,SAAS,EAAE,CAAC,mBAAmB,CAAC;QAChC,kBAAkB,EAAE,CAAC,EAAE,KAAK,EAAE,WAAW,EAAE,IAAI,EAAE,SAAS,EAAE,CAAC;KAC9D;CACF,CAAC,CAAC"}

package/dist/agents/nico.js

@@ -1,26 +1,20 @@
-// nico: a persona over the architect (master design §4). Everything not stated here
-// is the architect's.
+// nico: a persona over the business analyst (master design §4). Everything not stated here
+// is the business analyst's.
 import { persona } from '../compose.js';
-import { maintenance } from '../dimensions/communication-style/maintenance.js';
-import { semanticAddressing } from '../dimensions/expertise/semantic-addressing.js';
-import { parsimony } from '../dimensions/objective/parsimony.js';
-import { satisfice } from '../dimensions/objective/satisfice.js';
-import { analytical } from '../dimensions/stance/analytical.js';
-import { coldDecodeOracle } from '../dimensions/stance/cold-decode-oracle.js';
-import { invokeTheCanonical } from '../dimensions/stance/invoke-the-canonical.js';
-import { zeroTrust } from '../dimensions/stance/zero-trust.js';
-import { architectRole } from '../roles/architect.js';
-export const nico = persona(architectRole, {
+import { maintenance } from '../factors/communication-style/maintenance.js';
+import { terminology } from '../factors/expertise/terminology.js';
+import { parsimony } from '../factors/objective/parsimony.js';
+import { analytical } from '../factors/stance/analytical.js';
+import { zeroTrust } from '../factors/stance/zero-trust.js';
+import { businessAnalystRole } from '../roles/business-analyst.js';
+export const nico = persona(businessAnalystRole, {
     name: 'nico',
-    description: "Architect expert in the corpus and latent lexicography: finds the sign that most precisely and efficiently invokes each concept in a model's semantic space, read in its bounded context, and keeps the name a reader given the name with only its bounded context's name and subject decodes as meant.",
+    description: 'Business analyst expert in terminology: gives each concept of whatever project it is given its Cratylic name, with a precising definition only for the symmetric difference that remains.',
     mark: { emoji: '📐', hue: 'cyan' },
     values: {
-        objective: [
-            { value: parsimony, slot: 'drive' },
-            { value: satisfice, slot: 'stopping-rule' },
-        ],
-        expertise: [semanticAddressing],
-        stance: [analytical, zeroTrust, coldDecodeOracle, invokeTheCanonical],
+        objective: [{ value: parsimony, slot: 'drive' }],
+        expertise: [terminology],
+        stance: [analytical, zeroTrust],
         communicationStyle: [{ value: maintenance, slot: 'density' }],
     },
 });

package/dist/agents/nico.js.map

@@ -1 +1 @@
-{"version":3,"file":"nico.js","sourceRoot":"","sources":["../../src/agents/nico.ts"],"names":[],"mappings":"AAAA,oFAAoF;AACpF,sBAAsB;AAEtB,OAAO,EAAE,OAAO,EAAE,MAAM,eAAe,CAAC;AACxC,OAAO,EAAE,WAAW,EAAE,MAAM,kDAAkD,CAAC;AAC/E,OAAO,EAAE,kBAAkB,EAAE,MAAM,gDAAgD,CAAC;AACpF,OAAO,EAAE,SAAS,EAAE,MAAM,sCAAsC,CAAC;AACjE,OAAO,EAAE,SAAS,EAAE,MAAM,sCAAsC,CAAC;AACjE,OAAO,EAAE,UAAU,EAAE,MAAM,oCAAoC,CAAC;AAChE,OAAO,EAAE,gBAAgB,EAAE,MAAM,4CAA4C,CAAC;AAC9E,OAAO,EAAE,kBAAkB,EAAE,MAAM,8CAA8C,CAAC;AAClF,OAAO,EAAE,SAAS,EAAE,MAAM,oCAAoC,CAAC;AAC/D,OAAO,EAAE,aAAa,EAAE,MAAM,uBAAuB,CAAC;AAEtD,MAAM,CAAC,MAAM,IAAI,GAAG,OAAO,CAAC,aAAa,EAAE;IACzC,IAAI,EAAE,MAAM;IACZ,WAAW,EACT,ySAAyS;IAC3S,IAAI,EAAE,EAAE,KAAK,EAAE,IAAI,EAAE,GAAG,EAAE,MAAM,EAAE;IAClC,MAAM,EAAE;QACN,SAAS,EAAE;YACT,EAAE,KAAK,EAAE,SAAS,EAAE,IAAI,EAAE,OAAO,EAAE;YACnC,EAAE,KAAK,EAAE,SAAS,EAAE,IAAI,EAAE,eAAe,EAAE;SAC5C;QACD,SAAS,EAAE,CAAC,kBAAkB,CAAC;QAC/B,MAAM,EAAE,CAAC,UAAU,EAAE,SAAS,EAAE,gBAAgB,EAAE,kBAAkB,CAAC;QACrE,kBAAkB,EAAE,CAAC,EAAE,KAAK,EAAE,WAAW,EAAE,IAAI,EAAE,SAAS,EAAE,CAAC;KAC9D;CACF,CAAC,CAAC"}
+{"version":3,"file":"nico.js","sourceRoot":"","sources":["../../src/agents/nico.ts"],"names":[],"mappings":"AAAA,2FAA2F;AAC3F,6BAA6B;AAE7B,OAAO,EAAE,OAAO,EAAE,MAAM,eAAe,CAAC;AACxC,OAAO,EAAE,WAAW,EAAE,MAAM,+CAA+C,CAAC;AAC5E,OAAO,EAAE,WAAW,EAAE,MAAM,qCAAqC,CAAC;AAClE,OAAO,EAAE,SAAS,EAAE,MAAM,mCAAmC,CAAC;AAC9D,OAAO,EAAE,UAAU,EAAE,MAAM,iCAAiC,CAAC;AAC7D,OAAO,EAAE,SAAS,EAAE,MAAM,iCAAiC,CAAC;AAC5D,OAAO,EAAE,mBAAmB,EAAE,MAAM,8BAA8B,CAAC;AAEnE,MAAM,CAAC,MAAM,IAAI,GAAG,OAAO,CAAC,mBAAmB,EAAE;IAC/C,IAAI,EAAE,MAAM;IACZ,WAAW,EACT,2LAA2L;IAC7L,IAAI,EAAE,EAAE,KAAK,EAAE,IAAI,EAAE,GAAG,EAAE,MAAM,EAAE;IAClC,MAAM,EAAE;QACN,SAAS,EAAE,CAAC,EAAE,KAAK,EAAE,SAAS,EAAE,IAAI,EAAE,OAAO,EAAE,CAAC;QAChD,SAAS,EAAE,CAAC,WAAW,CAAC;QACxB,MAAM,EAAE,CAAC,UAAU,EAAE,SAAS,CAAC;QAC/B,kBAAkB,EAAE,CAAC,EAAE,KAAK,EAAE,WAAW,EAAE,IAAI,EAAE,SAAS,EAAE,CAAC;KAC9D;CACF,CAAC,CAAC"}

package/dist/agents/software-engineer.d.ts

@@ -0,0 +1 @@
+export declare const softwareEngineer: import("../manifest.js").Agent;

package/dist/agents/software-engineer.js

@@ -0,0 +1,5 @@
+// The software engineer role's generic holder: the role's profile, named for the role.
+import { holder } from '../compose.js';
+import { softwareEngineerRole } from '../roles/software-engineer.js';
+export const softwareEngineer = holder(softwareEngineerRole);
+//# sourceMappingURL=software-engineer.js.map

package/dist/agents/software-engineer.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"software-engineer.js","sourceRoot":"","sources":["../../src/agents/software-engineer.ts"],"names":[],"mappings":"AAAA,uFAAuF;AAEvF,OAAO,EAAE,MAAM,EAAE,MAAM,eAAe,CAAC;AACvC,OAAO,EAAE,oBAAoB,EAAE,MAAM,+BAA+B,CAAC;AAErE,MAAM,CAAC,MAAM,gBAAgB,GAAG,MAAM,CAAC,oBAAoB,CAAC,CAAC"}

package/dist/agents/tech-lead.d.ts

@@ -0,0 +1 @@
+export declare const techLead: import("../manifest.js").Agent;

package/dist/agents/tech-lead.js

@@ -0,0 +1,5 @@
+// The tech lead role's generic holder: the role's profile, named for the role.
+import { holder } from '../compose.js';
+import { techLeadRole } from '../roles/tech-lead.js';
+export const techLead = holder(techLeadRole);
+//# sourceMappingURL=tech-lead.js.map

package/dist/agents/tech-lead.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"tech-lead.js","sourceRoot":"","sources":["../../src/agents/tech-lead.ts"],"names":[],"mappings":"AAAA,+EAA+E;AAE/E,OAAO,EAAE,MAAM,EAAE,MAAM,eAAe,CAAC;AACvC,OAAO,EAAE,YAAY,EAAE,MAAM,uBAAuB,CAAC;AAErD,MAAM,CAAC,MAAM,QAAQ,GAAG,MAAM,CAAC,YAAY,CAAC,CAAC"}

package/dist/agents/test-engineer.d.ts

@@ -0,0 +1 @@
+export declare const testEngineer: import("../manifest.js").Agent;

package/dist/agents/test-engineer.js

@@ -0,0 +1,5 @@
+// The test engineer role's generic holder: the role's profile, named for the role.
+import { holder } from '../compose.js';
+import { testEngineerRole } from '../roles/test-engineer.js';
+export const testEngineer = holder(testEngineerRole);
+//# sourceMappingURL=test-engineer.js.map

package/dist/agents/test-engineer.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"test-engineer.js","sourceRoot":"","sources":["../../src/agents/test-engineer.ts"],"names":[],"mappings":"AAAA,mFAAmF;AAEnF,OAAO,EAAE,MAAM,EAAE,MAAM,eAAe,CAAC;AACvC,OAAO,EAAE,gBAAgB,EAAE,MAAM,2BAA2B,CAAC;AAE7D,MAAM,CAAC,MAAM,YAAY,GAAG,MAAM,CAAC,gBAAgB,CAAC,CAAC"}

package/dist/compose.d.ts

@@ -1,10 +1,10 @@
 import { type EnforcementLevel, type KebabToCamel, type Mark, type Value } from '@cratylus/schema';
-import { type Agent, type Dimension, MANIFEST } from './manifest.js';
+import { type Agent, type Factor, MANIFEST } from './manifest.js';
 /** The factors an agent holds a field for: every factor that is not an attribute. */
 type HeldFactor = {
-    [D in Dimension]: (typeof MANIFEST)[D]['arity'] extends 'attribute' ? never : D;
-}[Dimension];
-/** The field a held factor occupies on a role cell and a composed agent. */
+    [D in Factor]: (typeof MANIFEST)[D]['arity'] extends 'attribute' ? never : D;
+}[Factor];
+/** The field a held factor occupies on a role profile and a composed agent. */
 export type FactorField = KebabToCamel<HeldFactor>;
 /** A value as a role or persona states it: bare, or with its level, slot or note. */
 export type Stated<D extends string = string> = Value<D> | {
@@ -13,9 +13,9 @@ export type Stated<D extends string = string> = Value<D> | {
     readonly slot?: string;
     readonly note?: string;
 };
-/** A role: its full default vector, every non-attribute factor stated. */
-export interface RoleCell {
-    /** The role's anchor; the generic holder's name. */
+/** A role: its default profile, every non-attribute factor stated. */
+export interface RoleProfile {
+    /** The role's term; the generic holder's name. */
     readonly name: string;
     readonly description: string;
     /** The role's mark, which its generic holder carries. */
@@ -40,8 +40,8 @@ export interface Overrides {
 export declare class CompositionRefusal extends Error {
     readonly name = "CompositionRefusal";
 }
-/** The generic holder of a role: the role's vector, named for the role. */
-export declare function holder(cell: RoleCell): Agent;
-/** A persona over a role: the role's vector, then the persona's overrides and extensions. */
-export declare function persona(over: RoleCell, overrides: Overrides): Agent;
+/** The generic holder of a role: the role's profile, named for the role. */
+export declare function holder(profile: RoleProfile): Agent;
+/** A persona over a role: the role's profile, then the persona's overrides and extensions. */
+export declare function persona(over: RoleProfile, overrides: Overrides): Agent;
 export {};