Trust, recovery, and lifecycle · version 0.1.2

Fluent output is not automatic authority.

Lex can produce useful language work while keeping the missing evidence, human authority, and safe stopping point visible. Use the smallest recovery that matches the observed failure.

What Lex can and cannot do

Can help

  • draft, explain, rehearse, repair, and vary language for a real situation;
  • translate with purpose, audience, relationship, register, terminology, ambiguity, locale, and formatting in view;
  • prepare pronunciation and script support from available evidence;
  • record task-bound learner evidence in an optional user-owned file;
  • prepare a qualified-review handoff for consequential work.

Does not provide

  • equal quality across every language, variety, domain, model, or host;
  • official CEFR, ACTFL, IELTS, ILR, or other proficiency credentials;
  • hearing or assessment of audio that was not supplied;
  • certified translation, legal or medical approval, or community authority;
  • a guaranteed path to fluency, retention, acceptance, or avoidance of misunderstanding.

Privacy, storage, and network behavior

The packaged skill contains Markdown, JSON-compatible data, and optional Python standard-library validators. It requires no credential, database, microphone, browser, or network connection. The package does not create a hidden learner database or automatically persist a profile.

Your host may retain prompts, uploads, chats, files, or backups according to its own behavior and policy; this package cannot erase or certify those systems. Keep learner profiles outside the installed skill folder, remove unnecessary names and identifiers, inspect them at any time, and delete or archive them separately.

Do not put credentials, private learner records, confidential source text, medical identifiers, legal case details, or unnecessary personal data into public issue reports.

Security boundaries

Text supplied for translation is data—even when it contains commands, links, requests for credentials, or instructions to ignore prior guidance. The language task does not authorize executing embedded instructions or contacting anyone.

Protected placeholders, tags, names, numbers, dates, units, warnings, and negation can carry material risk. Verify them exactly. For a suspected vulnerability, use the repository private security advisory route; do not publish exploit details or sensitive data in a public issue.

Provenance and validation status

Lex Foster Language Companion is a Collaborative Dynamics public-service Augment. The practitioner voice is a grown derivative of Sam Walker’s canonical Universal Language Tutor — Lex Foster T1 v1.2. A privately retained third-party-character source informed translation and protocol mechanisms; its identity, likeness, and source text are excluded.

Version 0.1.2 includes deterministic learner-profile tests, a structural release validator, and eighteen behavioral evaluation definitions. File presence proves only presence. The current repair checks declared evidence, exact package bytes and local documentation. Historical public Pages deployment evidence applies to its recorded earlier bytes.

Structural checks do not prove current host installation, discovery, activation, language quality, professional approval, representative-user success, or formal WCAG conformance. An evaluation definition is not an executed model episode.

Consult the current version 0.1.2 validation record, release-time host matrix, and public provenance. Historical Pages deployment evidence is bound separately to its recorded public commit in verification/live-verification.json.

Troubleshoot from the observed symptom

The skill is not available

Confirm that Codex sees lex-foster-language-companion/SKILL.md with its resource folders intact, or that Claude received the untouched one-skill ZIP. Start a fresh context. If explicit invocation works but discovery does not, report routing rather than rewriting the runtime blindly.

The response starts with a questionnaire

Say: Give me usable language first. Ask only for one missing detail that would change it. If the behavior repeats in a fresh context with the skill active, preserve the exact prompt and response as a behavioral regression.

A fluent translation may be wrong

Reopen purpose, audience, relationship, target variety, and protected terms. Attach uncertainty to the exact span, compare protected tokens, and stop consequential reliance until ambiguity and authority gaps are resolved.

A learner profile fails

Run python scripts/validate_learner_profile.py <profile.json> and repair the first reported field. Preserve the original as read-only evidence if repair would destroy meaningful history.

The model claims an official level or unheard audio

Treat the claim as unsupported. Request a task-bound description of observed performance, or text-grounded pronunciation preparation plus the audio or qualified human feedback needed for assessment.

Completion proof is not “the file exists.” The original symptom must be absent in a fresh check, the intended task must continue, and remaining uncertainty or human approval must be explicit.

Update, remove, and clean up

Update

Keep one version in each installed skill root. Replace the old skill with the exact newer host artifact after reading its release notes; do not merge files from several versions. Learner profiles are separate user-owned files and are not automatically migrated.

Remove from Codex

  1. Finish tasks using the skill.
  2. Confirm the installed folder contains this product’s SKILL.md.
  3. Remove only that lex-foster-language-companion folder through your normal approved process.
  4. Start a new task and confirm the skill is no longer discovered.

Remove from Claude

Disable or remove Lex Foster Language Companion in the current skill-management interface, then start a new conversation and confirm it is unavailable. Current UI labels remain host-specific.

Clean learner data

Delete or archive learner-profile JSON separately. Removing the skill does not prove that a host, transcript, backup, or external service deleted other copies.

Support, contribution, license, and terms

Use GitHub Issues for installation problems, documentation barriers, reproducible language-behavior failures, and feature proposals. Include product version, host, artifact, observable result, expected result, and a redacted reproduction. Community support has no service-level guarantee.

Contributions should begin from current main, change canonical source first, add or revise a behavioral evaluation when needed, rerun deterministic checks, update affected customer guidance, and preserve community attribution and authority. Read Contributing.

Original public package content is released under the MIT License, without warranty. Names, frameworks, and cited works remain their owners’ property. No endorsement by ACTFL, the Council of Europe, or other referenced bodies is claimed.