HAAM Agent 01

Vercel runtime ready

A Vercel agent that can propose, but cannot publish.

Name: HAAM Documentation Steward
Author: HAAM

The HAAM Documentation Steward runs inside the HAAM Vercel project. It studies GitHub changes, detects documentation drift, and prepares evidence-backed pull requests while publication authority remains visibly human.

Read the operating guide Inspect the architecture

Published operating record

Proposal runs: 0
Code files reviewed: 0
Docs proposed: 0

Last published activity: Awaiting first configured Vercel run

The responsibility

Keep the public record aligned with the system.

Documentation drift is a quiet form of product failure. The steward turns repository changes into a bounded review, then creates a proposal only when the implementation provides enough evidence.

Review repository evidence

Vercel reads a bounded GitHub comparison and the current Fumadocs corpus.

Make a structured decision

The model must return evidence, confidence, risks, and complete MDX proposals in a strict schema.

Validate before writing

The runtime rejects unsafe paths, incomplete frontmatter, oversized output, and proposals that make no actual change.

Stop at human authority

The agent opens a GitHub pull request. It cannot merge or publish directly to rawdrafts.space.

Architecture

Vercel executes the work. GitHub preserves the evidence and approval boundary.

STEP 1

Vercel trigger

A secured daily Cron or authenticated API request starts the review.

STEP 2

GitHub evidence

The function compares commits and reads the current documentation corpus.

STEP 3

Structured review

The model returns a schema-constrained decision, evidence, confidence, risks, and MDX.

STEP 4

Proposal branch

Validated documentation and the evidence report are written to an isolated branch.

STEP 5

Human publication

A reviewer accepts, revises, or rejects the pull request before deployment.

Vercel Cron or manual trigger
        ↓
Vercel Function
        ↓
GitHub comparison + Fumadocs corpus
        ↓
OpenAI structured review
        ↓
validated documentation branch
        ↓
GitHub pull request
        ↓
human review
        ↓
rawdrafts.space/docs

Permission model

Useful enough to act. Bounded enough to trust.

Capability	Permission	Reason
Run on Vercel	Allowed	A daily secured Cron and an authenticated manual endpoint invoke the runtime.
Read GitHub changes	Allowed	The agent receives only the repository range needed for the review.
Read public documentation	Allowed	Current MDX is needed to detect drift and preserve context.
Edit content/docs	Proposal only	Changes remain isolated on an agent branch.
Create a pull request	Allowed	The pull request is the formal handoff to a human reviewer.
Edit application code	Blocked	Server-side validation restricts model output to documentation paths.
Merge or deploy	Blocked	GitHub review and the ordinary Vercel deployment remain human-controlled.

Latest public proposal

VERCEL RUNTIME READY

The code and schedule are deployed.

The first published record appears after Vercel environment variables are configured and a review produces a documentation proposal.

Build a governed agent

Give one recurring responsibility to a system that can explain every action.

HAAM designs agent workflows with explicit evidence, permissions, review gates, recovery paths, and visible operating records.

Start an agent project