Skip to content

APG v0.3.0

Choose a tag to compare

View all tags
@lair001 lair001 released this 22 Jul 10:16
· 7 commits to main since this release
v0.3.0
1a65061

APG v0.3.0 — Routed Workflows and Language-Aware Guidance

APG v0.3.0 expands Agentic Praxis Grimoire from six foundational process skills into a routed, language-aware engineering operating model with nineteen public skills.

The release adds thirteen capabilities while preserving the authority, evidence, privacy, provenance, and rollback boundaries established by earlier versions.

Release snapshot

  • 19 release-included skills
  • 14 stable skills
  • 5 provisional skills
  • 18 non-router capabilities
  • 13 newly published skills
  • 35 of 35 cross-repository dogfood cases matched
  • Fresh-session discovery and explicit-use smoke completed for all nineteen skills

Release inclusion remains independent of maturity: provisional skills are deliberately published as provisional rather than being promoted merely to simplify the release.

New workflow capabilities

APG workflow router

agentic-praxis-grimoire-workflow helps when:

  • multiple APG skills appear plausible;
  • an earlier routing decision needs audit; or
  • APG capability metadata may be incomplete or stale.

The router selects the smallest sufficient process skill or none. It does not bootstrap every session, mandate skill chains, override an explicit applicable selection, invent task authority, or own another skill's procedure.

Its checked capability map covers eighteen non-router skills and fails validation when the catalog grows without an explicit routing disposition.

Repository-guidance synthesis

synthesizing-repository-guidance analyzes dense, duplicated, mixed-scope, private, or source-derived guidance before rewrite.

It separates ownership, provenance, reuse rights, privacy, migration, rollback, and destination decisions. It does not silently rewrite source material, mirror private guidance, remove existing skills, or authorize a migration.

Approved-roadmap manager assignments

composing-approved-roadmap-assignments translates an already human-approved roadmap phase into a reviewable top-level manager assignment without expanding its authority.

Planning, routing, worker-assignment composition, dispatch, execution, review, and acceptance remain separate responsibilities.

Language, test, and database profiles

v0.3.0 introduces profile-based guidance for technology-specific judgment beyond repository policy.

Stable profiles

  • python-language-profile
  • bash-language-profile
  • bats-test-profile
  • zsh-language-profile
  • zunit-test-profile
  • nix-language-profile

The ZUnit profile is intentionally limited to the exact verified pairing of ZUnit v0.8.2 with Zsh 5.9.2. Zsh 5.3.1 is unsupported in the tested environment, and no broader compatibility range is claimed.

Provisional profiles

  • go-language-profile
  • ruby-language-profile
  • postgresql-database-profile
  • sqlite-database-profile

These profiles passed their retained evaluation requirements but remain provisional where the evidence does not yet justify stable maturity.

No generic SQL profile is introduced. PostgreSQL and SQLite retain distinct ownership because their transaction, locking, migration, recovery, operational, and file-ownership models materially differ.

Semantic phase and record identity

The new apg-check-record-identity command validates APG's semantic phase and durable-record conventions.

v0.3.0 formalizes:

  • semantic phase identifiers assigned before implementation;
  • independent ADR and exit-record sequences;
  • durable semantic references instead of development commit identities;
  • precommit record finalization; and
  • separation of public records from private operational Git evidence.

Source-specific lifecycle support

The release and user-management tools now support version-specific skill sets while retaining state schema version 1:

  • v0.2.0 sources declare six skills;
  • v0.3.0 sources declare nineteen skills;
  • update computes exact retained, added, and removed names;
  • rollback restores the previous source's exact declared set; and
  • historical v0.2.0 remains a valid immutable public source.

This avoids treating the current nineteen-name policy as though it had always applied to older releases.

Upgrading from v0.2.0

For an installation managed by apg-user-skills:

bin/apg-user-skills update --source <v0.3.0-public-checkout>
bin/apg-user-skills check

The update adds the thirteen v0.3.0 skills while preserving source identity, ownership state, retained links, rollback information, and unrelated user content.

Project-local installations can select all nineteen skills or an explicit subset:

bin/apg-project-skills install --repo <target-repository>
bin/apg-project-skills check --repo <target-repository>

A full Codex restart remains the fallback when discovery changes do not appear automatically.

Documentation

Assets 2
Loading