Release Gate
A commercial workflow surface for evaluating release readiness and retaining the evidence behind the decision.
Pilot-scoped ·RecursiveIntell Pro / pilot interest
Turn release evidence into an operating surface.
RecursiveIntell Pro is the commercial overlay described in the public agent-memory-kits project: release gates, patch verification, proof packets, Forge administration, and Agent Guard posture workflows.
01 / Published Pro scope
Five commercial surfaces.
The capability names below are grounded in the public agent-memory-kits Pro description. Details are intentionally bounded until deployment and license requirements are known.
Verify Patch
A focused patch-verification workflow that keeps inputs, checks, result state, and proof artifacts legible.
Pilot-scoped ·Proof packets
License-gated packaging of release and verification evidence for handoff, review, and retained inspection.
Pilot-scoped ·Forge admin MCP
Administrative MCP workflows for the Forge repair and verification surface, kept separate from ordinary agent authority.
Pilot-scoped ·Agent Guard posture
Posture reporting around the Agent Guard control-plane surface; reporting is evidence, not a security guarantee.
Pilot-scoped ·02 / Separate the lanes
Open foundation. Commercial workflow.
Pro does not put basic adoption behind a lead form. The public memory stack remains a direct install path; the commercial layer addresses release and administrative workflows.
| Surface | Open-source adoption | RecursiveIntell Pro interest |
|---|---|---|
| Agent memory | Public crates, host installation guidance, MCP adapters, and project documentation. | Uses the same public foundation; Pro is not required to begin installing memory. |
| Release decision | Public primitives can be composed by the operator. | Release Gate workflow and retained decision evidence. |
| Patch verification | Project-specific checks and public verification primitives. | Verify Patch workflow with a defined proof-packet boundary. |
| Administration | Public project interfaces and documentation. | Forge admin MCP and Agent Guard posture-reporting workflows. |
| Commercial terms | Governed by each public artifact’s declared license. | Pilot and license terms supplied directly after fit review. |
03 / Claim boundary
A proof packet is not a verdict.
Commercial packaging can make evidence easier to retain, review, and transfer. It cannot make an underlying result true by presentation alone.
Inputs, checks, state view, result, degradations, and retained artifacts can be made inspectable.
A successful workflow does not prove the absence of bugs or establish factual truth beyond its scope.
Posture reporting describes observed configuration and signals; it is not a penetration test or certification.
Release and administrative authority remains with the operator and the explicitly configured policy boundary.
Pilot fit
Start with one release path.
Describe the current release workflow, the evidence reviewers need, and the deployment boundary. A reply will confirm whether a Pro pilot or a services engagement is the better lane.