Skip to content

Add #698 vera shape to ROADMAP Phase 3a (Aver-inspired, paired with vera context)#699

Closed
aallan wants to merge 1 commit into
mainfrom
docs-roadmap-vera-shape
Closed

Add #698 vera shape to ROADMAP Phase 3a (Aver-inspired, paired with vera context)#699
aallan wants to merge 1 commit into
mainfrom
docs-roadmap-vera-shape

Conversation

@aallan

@aallan aallan commented May 26, 2026

Copy link
Copy Markdown
Owner

Summary

Adds #698 vera shape to ROADMAP Phase 3a (Agent integration), placed immediately after #523 vera context. The two are conceptual siblings:

  • vera context says what's here — token-budgeted public-API export for LLM consumption
  • vera shape says what shape it is — per-module histogram of function archetypes (match dispatcher / pipeline / orchestrator / pure helper / HOF wrapper / effect handler / Inference orchestrator / etc.) that maps onto architectural layers (domain / parse / command / AI-strategy / infra / handler)

Both directly inspired by Aver creator Szymon Teżewski (@jasisz1)vera context from the aver context command shipped earlier; vera shape from his 24 May tweet proposing aver shape.

Why this is more interesting in Vera than in Aver

Aver derives archetypes indirectly from what its grammar forbids (no if/else → match dispatchers; no loops → structural recursion). Vera permits if/else, loops, and lambdas, but adds three static signals Aver doesn't have:

  1. Declared effect rows — an effect orchestrator isn't just "a function that does side effects," it's "a function whose effect row is non-pure AND whose body is mostly effect calls." Combined those two signals are sharper than either alone.
  2. Typed slot references — structural-recursion detection is mechanical: "function calls itself with the same @T.k for some k strictly smaller than its own arity."
  3. Mandatory contracts — contract bodies are themselves analyzable; "contract-rich" is a real archetype that doesn't exist in languages without mandatory contracts.

So Vera's archetype categories are different from Aver's (we have Inference orchestrator and effect handler; Aver has neither since it has no algebraic effects).

Full design + Vera archetype list + classifier sketch in the issue body.

Why docs-only

Adds one bullet to ROADMAP.md Phase 3a. No code change. check_changelog_updated.py only fires for vera/ or spec/ changes, so no CHANGELOG entry needed. No version bump. No release after merge.

Test plan

  • git diff --stat ROADMAP.md — 1 file changed, 1 insertion(+)
  • Pre-commit hooks all green (mypy / pytest / etc. ran because of .pre-commit-config.yaml's default behaviour, even though no Python changed)

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Roadmap updated with Phase 3a milestone for a new planned CLI subcommand that classifies functions into archetypes and generates per-module histogram analysis, including baseline scanning for shape comparison workflows.

Review Change Stack

New entry in Phase 3a (Agent integration), placed immediately
after #523 vera context — both are Aver-inspired CLI tools for
LLM-agent project navigation.  Pairing them in the ROADMAP
reflects their conceptual relationship: context says what's
here, shape says what shape it is.

Credit Szymon Teżewski (@jasisz1) / Aver for the proposal —
this is the third Aver-inspired addition (after #523 vera
context and the broader CLI naming convention).  Vera's static
information is richer than Aver's (declared effect rows, typed
slot references, mandatory contracts) so the archetype
classifier has more signal to work with.

Docs-only PR — no version bump, no CHANGELOG entry needed
(check_changelog_updated.py only fires for vera/ or spec/
changes).

Co-Authored-By: Claude <noreply@anthropic.invalid>
@coderabbitai

coderabbitai Bot commented May 26, 2026

Copy link
Copy Markdown

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 43d14d39-1c1f-482d-8555-bc2d83ac5cc1

📥 Commits

Reviewing files that changed from the base of the PR and between cd4af3c and 99478f7.

📒 Files selected for processing (1)
  • ROADMAP.md

📝 Walkthrough

Walkthrough

The PR adds a single documentation entry to ROADMAP.md declaring the vera shape subcommand as a Phase 3a milestone. This new CLI tool classifies functions into archetypes and outputs per-module histograms, intentionally paired with existing vera context functionality for baseline shape comparison during validation scans.

Changes

Phase 3a vera shape roadmap entry

Layer / File(s) Summary
vera shape CLI subcommand milestone documentation
ROADMAP.md
Roadmap entry documents vera shape as a Phase 3a subcommand that classifies functions into archetypes and emits per-module histograms, with intended JSON output and initial validation scope paired to vera context.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

Possibly related PRs

  • aallan/vera#524: Both PRs modify ROADMAP.md to document Phase 3a entries; this PR completes the documented pairing by adding vera shape alongside the existing vera context milestone.

Suggested labels

docs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and specifically references the main change: adding the 'vera shape' feature to the ROADMAP under Phase 3a, with contextual details about its relationship to 'vera context'.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs-roadmap-vera-shape

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov

codecov Bot commented May 26, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.92%. Comparing base (cd4af3c) to head (99478f7).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #699   +/-   ##
=======================================
  Coverage   90.92%   90.92%           
=======================================
  Files          60       60           
  Lines       23606    23606           
  Branches      259      259           
=======================================
  Hits        21464    21464           
  Misses       2135     2135           
  Partials        7        7           
Flag Coverage Δ
javascript 57.43% <ø> (ø)
python 94.65% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@aallan

aallan commented May 26, 2026

Copy link
Copy Markdown
Owner Author

Consolidated into #697 — same shape (docs-only), no point in two parallel PRs. ROADMAP addition cherry-picked into #697's branch as commit 94ac7e2.

@aallan aallan closed this May 26, 2026
@aallan aallan deleted the docs-roadmap-vera-shape branch May 26, 2026 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant