Skip to content

README.md

Latest commit

 

History

History
125 lines (86 loc) · 3.65 KB

README.md

File metadata and controls

125 lines (86 loc) · 3.65 KB

SET logo

SET

Release Workflow License

SET is the thin orchestration layer in the ABVX stack.

It does not replace coding agents. It decides how repo tooling runs, makes workflow choices explicit, and keeps outputs predictable for CI and downstream agent flows.

What It Orchestrates

  • agentsgen for repo docs, pack artifacts, checks, and repo maps
  • ID for optional human-context hooks
  • proof-loop artifacts for durable review state
  • registry-driven workflow presets across repos

Quick Start

Use the action in a target repository:

- uses: markoblogo/SET@main
  with:
    workflow_preset: repo-docs
    path: "."

If you want a review-first planning pass before touching workflow files:

python3 scripts/plan_config_apply.py markoblogo/<owner>/<repo> --format json

Workflow Presets

  • repo-docs: init + pack + check
  • site-ai: repo-docs + site pack + analyze + meta
  • minimal: bootstrap-only baseline

ID Integration

When repo-local ID hooks are enabled, SET now does more than run pre_task.

It captures the resolved human bootstrap order and exports two runtime artifacts into the target repo:

  • docs/ai/id-bootstrap.json
  • docs/ai/id-bootstrap.prompt.md

These packets are built from the resolved ID hook output and are meant for downstream agent runs.

The JSON packet is now treated as a formal runtime interface, documented in docs/id-bootstrap.md, rather than as an action-only implementation detail.

Expected bootstrap order:

  1. soul.md
  2. profile.core.md
  3. handshake.md

SET also surfaces that order in the GitHub step summary.

Registry Contract

SET owns the orchestration registry and repo-config contract:

  • schema: schema/repo-config.v1.json
  • docs: docs/repo-config.md
  • runtime artifact docs: docs/id-bootstrap.md
  • examples: examples/repo-config.example.json
  • registry entries: registry/repos/*.json

Validate the registry with:

python3 scripts/validate_registry.py

Planning Mode

scripts/plan_config_apply.py is intentionally review-first:

  • shows the proposed workflow as structured output
  • exports planning artifacts such as plan.json, workflow.set.yml, and pr-body.md
  • can compare against a local repo root for drift
  • does not write target repositories directly

Useful commands:

python3 scripts/plan_config_apply.py markoblogo/lab.abvx
python3 scripts/plan_config_apply.py markoblogo/lab.abvx --dry-run --format json
python3 scripts/plan_config_apply.py markoblogo/lab.abvx --export-dir ./.set-plan
python3 scripts/plan_config_apply.py markoblogo/lab.abvx --repo-root /path/to/lab

Outputs

Depending on preset/config, SET can drive production of:

  • AGENTS.md, RUNBOOK.md
  • llms.txt / LLMS.md
  • docs/ai/id-context.json
  • docs/ai/id-bootstrap.json
  • docs/ai/id-bootstrap.prompt.md
  • repo maps and AI docs under docs/ai/
  • proof-loop artifacts under docs/ai/tasks/<task-id>/

Companion Layers

  • agentsgen: repo-scoped agent context
  • ID: portable human context
  • lab.abvx: public catalog/read-only surface

Key Docs

  • docs/repo-config.md
  • docs/id-bootstrap.md
  • docs/config-apply-planning.md
  • docs/llmo-capability-map.md
  • docs/v0.1-scope.md
  • CONTRIBUTING.md