Jordan-Hall / Jordan-Hall/browser

[P3][MEM-03] Verified workflow recipes and procedural learning

Open
#91 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Programme: #1
Epic: #29

## Objective
Convert repeated successful work into reusable tested procedures so the runtime becomes more deterministic and efficient over time rather than merely accumulating prompt history.

## Scope
- Detect candidate repeated workflows from successful verified task traces.
- Propose a `WorkflowRecipe` with inputs, preconditions, deterministic steps, bounded agent slots, required capabilities, budgets, stopping conditions and verification.
- User review/edit/approve before promotion to reusable automation.
- Versioning, migration, tests and rollback for recipes.
- Distinguish provider-independent logical steps from provider-specific adapters.
- Permission manifest and least-authority recomputation per run.
- Recipe simulator against EVAL-01 fixtures.

## Safety rules
- One successful click sequence does not become an unattended connector automatically.
- Promoting a recipe never promotes captured credentials/session cookies/old approvals.
- Recipe updates that widen capabilities require fresh review.

## Acceptance criteria
- [ ] Repeated verified task can produce a reviewable recipe proposal.
- [ ] Approved recipe declares exact inputs/capabilities/preconditions/verifiers.
- [ ] Recipe executes against resettable fixtures with bounded permissions.
- [ ] Captured secrets/approvals are absent from portable recipe definition.
- [ ] Update requiring broader authority stops for review.
- [ ] Failed recipe version can roll back without corrupting workspace/task state.

## Dependencies
- AGENT-01
- MEM-01
- SDK-01

**First phase:** P3
**Maturity target:** P5
**Owner:** workspace-ui-data

Contributor guide

No contributing guide indexed for this repository

Research direction

No files or entry points are named. Start by reading the AGENT-01, MEM-01 and SDK-01 dependencies and the EVAL-01 fixtures, then map the proposed WorkflowRecipe lifecycle and its review, permission, verification and rollback boundaries. Done means all listed acceptance criteria are covered, including resettable-fixture execution and safe handling of secrets and authority changes.

Written by the indexing model from the issue text.

Assessment

Domain
backend, security, testing, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.