Adaptive Grok Build Pro v2.0.15 — pre-pilot technical preview

Adaptive Grok Build Pro v2.0.15

Governed Agentic Software Factory — pre-pilot technical preview.

Delivered

• PR #27 adds the separate pilot/ single-operator capability: one allowlisted GitHub issue snapshot, an exact private source clone, one pinned Codex app-server turn, a sealed candidate, one configured test command plus independent semantic validation, and separately delegated non-force branch/draft-PR publication.
• A closed pilot_confined command profile is checked by real no-model sandbox probes. Durable SQLite intents make ambiguous external-effect recovery observation-only; automatic model retries remain disabled.
• Review repairs cover CSP digest validation, actual pilot-test discovery, command read isolation and architecture ownership. The downstream OpenClaw workspace-path discovery report is preserved under engineering/backlog/20260905-openclaw-workspace-path-discovery.md for a separate repair.
• M0–M9 repository source delivered in v2.0.13 and the v2.0.14 offline multimodal artifact remain included. This release does not claim operational M8/M9 activation.

Exact delivery evidence

• Pull request: #27
• Checked head: 9fcc9d943c74260c02a920a59490143f91cb38b2.
• Protected squash merge: fd51dcfed6b33f4a8707c0db602328146df17cc9 at 2026-09-05T20:14:37Z.
• Identical checked/merged tree: f01e9b0d1f80fb6731c68079540fd98e5c1f64ac.
• GitHub App 4694114, check adaptive-trust-ci/verified@06ecf1c875bc, run 101365945968: SUCCESS at 2026-09-05T20:08:36Z. Attestation 4a13e71c-25e7-4272-80fa-8153590edc84, signer 0519cf1d47436f2e.
• GitGuardian run 101365931711: SKIPPED after the operator marked incident 36975026 as a false positive. The value is a public CSP fixture digest, not a credential. This is not represented as a fresh successful secret scan.
• Local affected-continuation verification and all three independent reviews passed on the checked head. The original PostgreSQL timeout and subsequent targeted successful recovery remain preserved; this does not claim a second complete local test run.
• The source-parent build was reproduced in two private no-local clones. The ZIP was then reproduced byte-for-byte from the exact protected merged commit before publication.
• ZIP SHA-256: 1f0f64557fd258df7e533f674bb4e7c55d4a1a51454d48bcfecfa5487d08e9d7.
• Sidecar SHA-256: 8f3ed4b8eb96f7984eb38b0c988bd8a8cee8cdc789bca52527084b78fd791c6d.

Explicit limits and next step

No real model attempt, target-repository change, automatically created target PR, deployment, hosted-site publication, M8 accepted cohort or M9 live qualification is claimed. The pilot is default-unavailable. Its first live attempt is blocked because the pinned landing base 6990103 advanced to observed 80d6215; refresh the trusted target scope while preserving the newer analytics and deployment-archive coherence before spending one model attempt. The target repository has no configured App-owned Trust CI profile, so a future proposal cannot claim merge eligibility.

The tag preserves the reviewed pre-publication source snapshot: its README/START_HERE/PROJECT_STATE candidate wording is historical, and these release notes record the completed delivery. A separate documentation-only successor will synchronize current-main handoff without replacing the immutable ZIP or retagging this release. Older PRs #12/#13/#15 are being reconciled for unique work, not silently discarded.

Rollback is selection of the immutable v2.0.14 package/tag; this publication performs no runtime or database mutation. Published v2.0.13/v2.0.14 artifacts are unchanged.

Adaptive Grok Build Pro v2.0.14

L5 multimodal landing-factory MVP: bounded authenticated text, audio, image, PDF and DOCX intake; pinned closed-spec provider boundary; at most three isolated render/evaluation attempts; deterministic artifact sealing; and a disabled-by-default publication port. The shipped default performs no provider call, hosting mutation, or production deployment. PR #24 passed the App-owned adaptive-trust-ci/verified@06ecf1c875bc gate on the exact reviewed head. ZIP SHA-256: b03c64e67ac757f7d84abfed407cbd0ace2771afd960c67e24684099b3cc0264.

Adaptive Grok Build Pro v2.0.13

Adaptive Grok Build Pro 2.0.13 delivers the integrated M4-M9 control plane and packaged product.

Highlights:

• M9 staged local delivery, deterministic recovery, terminal-state handling, and bounded retry/human-escalation behavior.
• Integrated M4-M8 control-plane capabilities and database migrations 001-018.
• Reproducible ZIP built independently in two private no-local clones.

Verification:

• PR #22 exact head: b5eba75
• Merged commit: 8599d45
• Tree: 03e122a30fb2dbb59907f4c4c28e17f93cbf0751
• App-owned Trust CI: adaptive-trust-ci/verified@06ecf1c875bc — SUCCESS
• ZIP SHA256: 3d5179f589c507143f4b93a98d2518e37e470e8566a62f77b31c35743ed8240c

Production-provider writes remain deliberately approval-gated; this release does not embed production credentials or grant provider mutation authority.

Adaptive Grok Build Pro v2.0.12

2.0.12 — 2026-08-23

Self-hosted Trust CI control plane in-tree, K16 README graph, optional docker/syft/trivy/cosign toolchain pins.

• Product identity 2.0.12; Trust CI service identity stays 2.1.0
• PR-only delivery; rebase-merge of draft PR #2 is a bootstrap exception because the App-owned check is not live yet
• Example image pins stay placeholders; live registry pins stay untracked
• Still no GitHub Actions

Adaptive Grok Build Pro v2.0.11

2.0.11 — 2026-08-17

Skip the analysis/review wave when nothing product-changed; always push main and release when green.

• AGENTS.md: Skip no-op checks; Release when green now names git push origin main
• Same product surface as 2.0.10 plus this contract
• Still no GitHub Actions

Adaptive Grok Build Pro v2.0.10

2.0.10 — 2026-08-16

Published identity of current main after v2.0.9.

• Same product surface as 2.0.9 plus this version identity
• Standing rule still: green verify → new release
• Still no GitHub Actions

Adaptive Grok Build Pro v2.0.9

2.0.9 — 2026-08-16

Published identity of current main after v2.0.8.

• Same product surface as 2.0.8 plus this version identity
• Standing rule still: green verify → new release
• Still no GitHub Actions

Adaptive Grok Build Pro v2.0.8

2.0.8 — 2026-08-16

Agent self-learning, root memory files, and a complete-graph README.

• AGENTS.md starts with log-to-root decisions.md / mistakes.md
• Standing rules: refresh README before every push/deploy; split large tasks; share AGENTS.md / decisions.md / mistakes.md; publish a new release when verify is green
• README is the product map: Current state, Read first, Map, K10 complete graph
• Structure tests lock those placements
• Still no GitHub Actions

Adaptive Grok Build Pro v2.0.7

2.0.7 — 2026-08-16

Leftover 2.0.6 product fixes, published as their own release.

• install_into copies ruff.toml, bandit.yaml, and .coveragerc
• grok_deploy prints --title "Adaptive Grok Build Pro v…"
• package_stack unlinks leftover root MANIFEST.sha256 after the zip embeds it
• __version__ matches VERSION
• Stop hook wording is warn-only
• Still no GitHub Actions

Adaptive Grok Build Pro v2.0.6

2.0.6 — 2026-08-16

Quality contour: Ruff, Bandit, coverage ratchet, no GitHub Actions.

• grok_verify runs Ruff from ruff.toml without a packaging marker; skip-if-missing, fail-closed when ruff/bandit/coverage are installed
• Bandit AST next to regex secret-scan; excludes tests/ and engineering/
• Coverage.py report in pr/release after a measured fail-under of 74 (ratchet, not a guessed 90)
• No GitHub Actions / Dependabot; local python3 scripts/grok_verify.py --mode pr is the only gate. --with-ci is forbidden.
• Optional consumer Semgrep / Trivy config / npm prettier|format when those signals exist; not enabled on this tree