Fructal Cap Design

Open workflow engineering method · 1.2.0

Keep the boundary. Fix the motion.

A necessary constraint should guide completion, recovery, and handoff—not make people wrestle with the system around it.

Activation boundary

Workflow obstruction, not every constraint.

Use it

When the handling of a necessary rule or limit causes avoidable loss of progress, context, or ownership. Identify the retained constraint and the obstruction; a credible report can justify investigation.

Scale it

Use a compact pass for local reversible friction and a deeper trace when consequences, uncertainty, actors, or irreversibility increase. Even one defective control can qualify; size and actor count do not decide.

Do not activate

For aesthetics, ordinary requirements, or local defects without that constraint–obstruction connection. Continue the task with ordinary design or debugging instead.

Three runnable examples

Name the mode and the boundary.

Review

Use $fructal in Review mode. Review this blocked handoff without changing it: [workflow]

Redesign

Use $fructal in Redesign mode. Redesign this constrained recovery path: [workflow]

Implement

Use $fructal in Implement mode. Implement and verify this authorized workflow repair: [change]

Agent Skills installation

One repository. One canonical skill.

Install with the open Agent Skills CLI. Host-specific instructions and exact alternatives are in the repository README.

DISABLE_TELEMETRY=1 npx skills add PaolaShultz/shr-skills

Retained evaluation evidence

A simpler contract, with its evidence limits visible.

Version 1.2.0 simplifies the contract while keeping all six questions. Read the release notes. The historical 1.1.1 matrix and critical repetitions separate natural execution from semantic judgment. Those older runs do not validate 1.2.0. They are bounded regression evidence, not scientific proof or independent validation: the evaluator was another isolated run of the same model family, and affected-user acceptance remains outside the archive.

External evaluation wanted

Bring the cases that should break it.

Challenge activation, authorization, mode boundaries, recovery, and cross-actor continuity. The issue form asks only for a reproducible workflow case and explicitly excludes secrets, personal data, proprietary material, and harmful content.

Submit an adversarial case