← Browse

@aryaniyaps/lamina-user-modeling

A

Create evidence-grounded Persona and Actor resources and compile independent graph Missions without treating simulations as research.

skillclaude

Install

agr install @aryaniyaps/lamina-user-modeling --target claude

Writes 1 file into .claude/skills/, pinned to git-6427b2a1.

  • .claude/skills/lamina-user-modeling/SKILL.md

Document


name: lamina-user-modeling description: "Create evidence-grounded Persona and Actor resources and compile independent graph Missions without treating simulations as research."

User modeling

Business documents and .lamina/personas.json are indexable evidence. Canonical Personas and Actors are Resource records in Ladybug:

  • Actor expresses authority, ownership, identity proof, and allowed Operations.
  • Persona expresses goals, constraints, context, and evidence.
  • Link them with a typed Statement such as lamina:canAssume.

Use explicit input, research, analytics, support evidence, or brownfield observations. Keep agent inference epistemically inferred and Persona interpretation simulated. Do not invent demographics or preferences that do not change behavior.

Before implementation, run one independent lamina design prepare-walk task per active Persona and record the isolated result with lamina design record-walk. These design-time simulations walk every proposed operation, including denied and inapplicable nodes, and may expand the graph with missing permissions, states, Scenarios, Invariants, and recovery paths. Rerun all affected walks until a current full round returns empty discovery arrays.

After implementation, compile one independent runtime Mission for every active Persona with lamina mission compile. There is no maximum. Each Mission gets an isolated Run and adapter context. Design simulations and runtime Missions are different evidence classes. Preference findings remain hypotheses; only structural, safety, contradiction, observed, human, or runtime evidence may support stronger claims.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-6427b2a14d192026-07-31