Skip to content

markoblogo/lab.abvx

Repository files navigation

ABVX Lab

A static hub and read-only control plane for ABVX developer tools. The home page acts as an editorial index: SET is the orchestration entrypoint, the control plane is summarized in a compact snapshot, and the tool catalog is grouped by role.

Live: lab.abvx.xyz

ABVX Lab cover

Home page structure

Tool groups

Orchestration

  • SET — Thin GitHub Action entrypoint for presets, repo-docs, site-ai flows, registry-driven review, and proof-loop orchestration.

Repo docs & agent context

Validation & CI

Analysis & LLMO

  • repomap — Token-budgeted repo map + import graph artifacts with relevance ranking and slice modes.
  • agentsgen analyze — Planned public surface for AI-visibility scoring of a public URL.
  • agentsgen meta — Planned public surface for SEO + AI metadata generation.

Release & publishing

  • git-tweet — Turn git changes into tweet-sized release notes.

Utilities

Agentsgen family naming

Agentsgen commands are presented here as separate tool pages for discoverability. They still ship together as one package: agentsgen.

Control plane surfaces

  • What to review next — Read-only planning queue with status, priority, workflow-sync hints, operator queue, and richer proof-loop readiness signals from the SET planner.
  • Proof queue — Read-only proof-loop queue for blockers, review-ready tasks, evidence quality, and recommendations.
  • Repo cards — Aggregated view combining registry baselines, latest workflow status, workflow sync, repomap metadata, and proof status.
  • Registry snapshot — Read-only view of repo baselines from the SET central registry.
  • Workflow status snapshot — Read-only latest GitHub Actions run per registered repo plus sync state, operator queue, and proof status.

Maintenance

What's inside

  • Registry snapshot generator: scripts/sync_registry_snapshot.py
  • Workflow status generator: scripts/sync_status_snapshot.py
  • Repo cards generator: scripts/build_repo_cards_snapshot.py
  • Planning snapshot generator: scripts/sync_planning_snapshot.py
  • Proof snapshot generator: scripts/sync_proof_snapshot.py
  • Snapshot outputs:
    • docs/registry/index.html
    • docs/assets/registry-snapshot.json
    • docs/status/index.html
    • docs/assets/status-snapshot.json
    • docs/repos/index.html
    • docs/assets/repo-cards-snapshot.json
    • docs/planning/index.html
    • docs/assets/planning-snapshot.json
    • docs/proof/index.html
    • docs/assets/proof-snapshot.json
  • Home page: docs/index.html
  • Tool pages: docs/tools/<slug>/index.html
  • SEO basics: docs/robots.txt and docs/sitemap.xml
  • Theme assets: docs/assets/asciitheme.css, docs/assets/ascii-theme.js

Snapshot behavior

  • Planning, repo cards, and status surfaces can include workflow sync state and operator queue when planning artifacts are present.
  • Planning, repo cards, and status surfaces can also show compact repomap status, policy modes, active slices, slice source labels, and top ranked files when local repo artifacts are available.
  • Proof queue and related surfaces remain snapshot-based: they reflect the latest local rebuild, not a browser-side live GitHub read.

Tool pages (routing)

Visual system

ABVX Lab uses a minimal static setup with vendored AsciiTheme assets:

  • docs/assets/asciitheme.css is the base preset
  • docs/assets/ascii-theme.js provides the theme toggle
  • Home page styling now lives inline in docs/index.html to keep the editorial layout self-contained

How to add a new tool

Use this checklist:

  • Create a new tool page from an existing docs/tools/<slug>/index.html
  • Update the title, one-liner, links, metadata, and canonical URL
  • Add the tool entry to docs/index.html in the right group
  • If it is the newest tool, move it to the top of its group and optionally mark it NEW
  • Add the tool URL to docs/sitemap.xml
  • If the tool has a live site, add its live link on both the home entry and the tool page

Deploy

GitHub Pages publishes this site from /docs on main.

Flow: commit -> push -> wait for Pages.

If you change asset URLs or ship a static asset that browsers may cache aggressively, add or update the cache-busting query suffix in the HTML.