Skip to content

VM4AI AIR Kit v0.2.1

Choose a tag to compare

View all tags
@eddlev eddlev released this 14 Jun 23:41
v0.2.1
b74d25e

VM4AI AIR Kit v0.2.1

This release patches AIR's prompt-runtime behavior around deterministic onboarding, capability-layer need detection, and AIR Method Layer routing.

It builds on v0.2.0's public prompt-kit refresh and keeps the same scope boundary: AIR Kit remains a prompt-only, user-loadable framework for structured AI-assisted project work. It does not claim backend validation, runtime enforcement, signed contracts, autonomous agent execution, or empirical performance improvement.

Highlights

  • Added deterministic onboarding non-inference doctrine.
  • Clarified that Q1 is a branch selector, not an intent classifier.
  • Prevented host models from inferring Q1=A from activation text such as "Start a new AIR project."
  • Preserved Q1-D as an instructional tutorial branch that must return to Q1 before activation.
  • Added capability-layer need detection for specialists, domain packages, and method packs.
  • Clarified that AIR should request or offer capability layers when needed instead of expecting users to know.
  • Added AIR Method Layer doctrine.
  • Clarified that task-local procedure belongs in AIR_ARTIFACT.method by default.
  • Clarified that reusable AIR_METHOD_PACK promotion happens only when justified by recurrence, low variance, portability, template need, or defect/rework history.
  • Added Control Surface rendering for deterministic onboarding checks, capability-layer checks, and method-layer state.
  • Updated Default Starter awareness for deterministic onboarding, capability-layer detection, and method-layer behavior.
  • Updated Handoff Card Template to preserve onboarding, capability-layer, and method-layer state across sessions.
  • Updated README, roadmap, and user guide documentation for the new behavior.

What changed

Deterministic onboarding

AIR onboarding questions are now explicitly protected from host-model inference.

Start a new AIR project may trigger first activation flow, but it must not silently answer Q1 as A. New project.

Q1 must be:

  • explicitly answered by the user
  • restored from a valid handoff card
  • proposed visibly by AIR and approved by the user

This protects import flow, handoff flow, and tutorial-flow testing from being bypassed.

Capability-layer need detection

AIR now has explicit doctrine for detecting when the Default Starter is not enough.

AIR may recommend:

  • a specialist profile for reusable capability posture and judgment
  • a domain package for terminology, standards, evidence expectations, model/platform facts, and claim boundaries
  • a method pack for reusable ordered procedure

AIR may recommend automatically, but generation still requires explicit user approval and binding requires validation/routing fit.

AIR Method Layer

The applied method for a task belongs in:

AIR_ARTIFACT.method

This keeps one-off procedures fitted to the active task.

Reusable AIR_METHOD_PACK files are promoted only when a method proves reusable, low-variance, portable, template-bearing, or defect-reducing.

A Method Pack standardizes procedure. It does not prove the procedure executed and does not provide backend validation.

Scope boundary

This release does not claim:

  • backend enforcement
  • signed AIR contracts
  • runtime validation
  • autonomous agent execution
  • tool execution
  • empirical AIR performance improvement
  • provider-independent reliability

AIR Kit v0.2.1 remains a public prompt/profile/documentation kit.

Recommended use

Use the standard new-project boot bundle:

  • prompts/AIR CORE RUNTIME.md
  • prompts/AIR CONTROL SURFACE.md
  • prompts/AIR DEFAULT STARTER PROFILE.json

Then type:

Start a new AIR project.

AIR should ask Q1 rather than infer it.

For continuation, attach:

  • prompts/AIR CORE RUNTIME.md
  • the previous AIR_HANDOFF_CARD

Optionally attach:

  • prompts/AIR CONTROL SURFACE.md

Upgrade notes

Replace or pull the updated prompt files and documentation.

If you maintain your own AIR handoff templates, add fields for:

  • deterministic onboarding state
  • capability-layer need state
  • method-layer state
  • recommended method packs
  • generated method packs pending validation
  • validated available method packs
  • active method pack

Suggested regression check

After loading the v0.2.1 prompt files, test:

Start a new AIR project.

Expected behavior:

  • AIR begins first activation flow.
  • AIR emits required boot evidence if configured to do so.
  • AIR asks Q1.
  • AIR does not infer Q1=A.
  • If Q1-D is selected, AIR explains itself and returns to Q1 without activating a project.
Assets 2
Loading