Fenroth / ForgeAI

Fenroth presents

ForgeAI - The Verified AI Software Engineer

Analyze repositories, identify root causes, generate evidence-backed repairs, verify changes, request explicit approval, and apply updates safely with rollback protection.

Explore ForgeAIOpen Mission Control

Verified Engineering Workflow

ForgeAI Level 0 emphasizes evidence, explicit authorization, and truthful reporting before any repository mutation occurs.

  1. Step 1

    Repository Context

  2. Step 2

    Root Cause Analysis

  3. Step 3

    Evidence-Backed Patch

  4. Step 4

    Dry-Run Verification

  5. Step 5

    Explicit Approval

  6. Step 6

    Authorization

  7. Step 7

    Safe Patch Execution

  8. Step 8

    Rollback Protection

  9. Step 9

    Truthful Result

Core Capabilities

Repository analysis

Implemented

Workspace and repository context inspection for planning.

Deterministic root-cause analysis

Implemented

Root-cause findings oriented around deterministic signals.

Evidence-backed patch generation

Implemented

Patch plans include evidence and proposal metadata.

Dry-run verification

Implemented

Planning and verification stages run before mutation.

Explicit approval + authorization

Implemented

Execution requires explicit approval and authorization payloads.

Safe patch execution + rollback

Implemented

UPDATE_FILE execution with preconditions and rollback reporting.

CREATE_FILE / DELETE_FILE execution

Planned

Planned after Level 0 launch validation.

Hosted SaaS accounts

Planned

Not available in Level 0.

Team collaboration + enterprise SSO

Planned

Planned for future phases.

Current Level 0 Availability

ForgeAI Level 0 is production validated on Windows through CLI and Mission Control workflows. Hosted, self-serve SaaS accounts are not available yet; access is currently coordinated through early access.

Safety and Approval Model

  • Planning-only by default with default-deny execution
  • Proposal-bound approval and approved operation IDs
  • Repository-root containment, path traversal rejection, and symlink rejection
  • SHA256 and byte-size preconditions before mutation
  • Atomic write path with rollback on post-write failure
  • Command verification recommendations remain NOT EXECUTED
  • Execution summaries are sanitized to avoid source or secret exposure

Current Availability

Level 0 has reached production validation on Windows

ForgeAI Level 0 is validated for Windows local and CLI-driven workflows. Public self-serve installer distribution and commercial pricing are still being finalized for a controlled early-access rollout.

Join Early AccessOpen Local Mission Control