Cory Workbench

AI teammate with a human gate

Cory turns requests into governed work.

It preserves Slack and Linear intake, drafts the right workflow, waits for approval, then records GitHub PR evidence.

Open workspace View workflow

Sample governed request

Control-plane state

Plan First

A single request is interpreted, approved, executed, reviewed, and retained.

Slack intake

Build Cory public site

Scope drafted from thread, plan, repo context, and non-goals

Interpretation

Approved taskMarketing surfaceNo deployNo policy change

Approval gate

Human-approved scope is required before the dev run can start.

Bounded run

Branch pushed

Tests recorded

Review handoff

KM candidate

Retain decision and workflow evidence

Evidence linked

Current intake starts in Slack or Linear. GitHub remains code and PR truth.

Slack thread intake

Linear issue intake

GitHub PR evidence

Cory Workbench approval

The problem

Agents are fast. The work around them is still ambiguous.

Software teams already have the signals. The hard part is deciding what a request means, who may approve it, and what evidence survives after delivery.

Requests arrive fragmented

Slack has the intent, Linear has priority, and GitHub has code truth. No single place explains the work.

Execution starts too early

Ambiguous asks become coding runs before scope, non-goals, risk, and approval are visible to the team.

Learning disappears

The rationale, blocker history, verification, and review evidence often vanish into chat history or PR comments.

The redesign shifts Cory from AI landing page to trust control plane.

The page keeps the dark mint brand, but reduces repeated card grids, adds evidence and risk color states, and turns the hero into durable workflow state.

Taste-led audit, not template copying

Design variance, motion, and density are tuned for a B2B control plane instead of copying a high-motion template.

Asymmetric workflow visual

The hero visual now reads as assignment, contract, evidence, and handoff state instead of a generic screenshot.

Evidence palette

Mint stays the main brand signal, amber marks approval or pending work, and rose marks risk without changing the whole theme.

Shorter CTA intent

The same workspace and workflow actions appear in the hero, nav, and final section without competing labels.

Workflow

Interpret first, gate side effects, keep the evidence.

Cory separates intelligence from governance. The agent drafts and executes, while the control plane owns state, approval, audit, and durable knowledge.

Capture intake

Preserve the raw Slack thread or Linear issue signal before semantic judgment.

Original context stays attached.

Interpret intent

Cory decides whether the thread needs a plan or discussion, drafts scope, proposes repo context, and exposes uncertainty.

Humans review a draft, not a blank form.

Approve the plan

Risky work waits for a bounded approval with explicit non-goals and verification expectations.

Side effects are intentional.

Execute in bounds

Coding agents receive the approved contract and report progress, blockers, branch state, and checks.

Delivery remains reviewable.

Retain knowledge

Decisions, runbooks, and reusable context can become governed KM candidates for the workspace.

The next request starts smarter.

Code as agent harness

Cory makes agent work inspectable before it becomes company work.

The business value is a code-backed coworker harness: assignment intake, workflow contracts, permissioned actions, artifacts, evidence, and repairable blockers.

Business translation

CTO

Operational truth

Know what the agent did, what it could not verify, and which state owns the answer.

Scope before spend

Review the interpreted job, non-goals, and approval boundary before engineering time starts.

Engineering lead

Bounded agent runs

Coding agents receive a contract with owned paths, verification expectations, and handoff evidence.

Founder or COO

Reusable memory

Decisions and artifacts survive the Slack thread so the next request starts with context.

Harness objects Cory can project

assignment_intake

Turns a request into outcome, source of truth, assumptions, and ask-first boundaries.

workflow_contract

Defines stages, allowed side effects, approval gates, and repair paths.

artifact + evidence

Stores inspectable results, commands, branch state, review findings, and public previews.

unable_to_verify

Reports missing evidence as a repairable state instead of pretending work is done.

Current boundary

Today, Cory is scoped to Plan First work and thread context.

The public site describes the MVP that exists now: Slack-thread planning, human approval, PR handoff, and contextual discussion. Broader request taxonomies stay roadmap until they are shipped.

Plan First

Live MVP

Slack thread to approved plan

A concrete code request becomes a scoped plan with acceptance criteria, non-goals, and the right repo context before any coding run starts.

Human gate

Live MVP

Approval before PR work

Cory waits for the plan approval gate, then sends bounded work to coding agents and records branch, verification, and review handoff evidence.

Discussion

Live MVP

Thread-context answers

Architecture and requirements questions stay in the conversation path when the team needs judgment, not a new implementation ticket.

Roadmap

Post-MVP

Broader governed routing

Multi-shape routing and governed knowledge promotion belong to the v0.2 direction and are not presented here as current execution capability.

Ideal customer profile

Built for teams where delivery context and review discipline matter.

Cory fits organizations that already use collaborative tools and agents, but need a governed system of record for how work moves.

CTO and platform owner

Operational control

See what is waiting, blocked, running, or ready for review without reconstructing status from raw logs.

PM and product lead

Higher-fidelity intent

Review scope, non-goals, and clarification before engineering work starts.

Engineering lead

Safer agent handoff

Receive bounded work with approval state, repo context, verification expectations, and evidence.

Founder or COO

Less organizational memory loss

Keep the decisions behind shipped work available to the team after the thread is over.

Value proposition

Cory creates leverage by improving judgment, not bypassing it.

The product is valuable because it turns messy collaboration into governed work while keeping humans responsible for durable decisions.

Interpretation before execution

Requests become structured drafts with visible ambiguity, context, and non-goals.

Teams approve the right scope of work before any side effect.

Approval before side effects

Durable actions require explicit gates and leave audit evidence.

Runners receive a bounded contract instead of guessing policy.

Knowledge after delivery

Evidence, rationale, and runbooks can move into governed workspace memory.

Future requests inherit context instead of restarting from chat.

Motion should communicate workflow state.

This implementation keeps runtime motion in CSS and reserves GSAP for a later isolated client leaf when a pinned workflow stack is approved.

Current

CSS reveal and state pulse

Only transform and opacity animate, so the signed-out page stays server-rendered and reduced-motion safe.

GSAP

Sticky workflow stack

Use GSAP ScrollTrigger only for assignment to contract to evidence storytelling, with cleanup and reduced-motion fallback.

Guardrail

No decorative motion

Hero, evidence, and blocker motion must explain hierarchy, transition, or state. Everything else stays still.

Cloudflare is the marketing path, not a full control-plane migration claim.

The safe next step is Cloudflare Pages for static marketing previews. The Node control plane stays on its current runtime until API routes, auth, Postgres, and runner orchestration are verified.

Pages

Static marketing preview

Use branch previews, cacheable assets, and rollbacks for the public site slice.

Channel-safe media

Store transformed public images or short demo media after removing private repo and Slack material.

Workers

Bounded edge surfaces

Use Workers for redirects, public artifact proxying, or webhook guards before considering app runtime changes.

Data

Postgres remains truth

Do not replace durable workflow state with KV or D1 without a separate architecture decision.

Give Cory one governed front door.

Use Cory Workbench to interpret requests, coordinate approval, and keep evidence attached to the work.

No auto-mergeNo auto-deployApproval before side effects