Renigma
Preserve what matters. Inspect what changes.
A workbench connecting language, context, operations, scenarios, evidence, and human control.
Explore the project studyWorkflow research
Mission Lab
A process with a record of why.
A Python controller connecting structured file-audit requirements to plans, execution, receipts, and revision.
INDEPENDENT PORTFOLIO PROJECT
Context & intent
A workflow needs more than a list of actions. Dependencies, resource limits, and acceptance conditions influence which execution path is appropriate.
Make a small execution lifecycle explicit enough to inspect and revise.
Project context and development approach
This is an independent project from my portfolio across FractalDesignZ and ZuluYokohama. My practice centers on directing work with substantial assistance from agentic AI and development harnesses. The mechanisms and evidence below describe this project; they do not attribute every component to manual authorship or a specialist review.
Implemented mechanisms
- Structured specifications retain requirements, acceptance conditions, evidence references, and unresolved questions.
- Dependency graphs and deterministic planning connect registered operations under worker and declared buffer limits.
- File hashing, comparison, and manifest assembly produce verification receipts. Resource revisions invalidate affected downstream work.
Evidence & merit
Source review describes implementation; recorded tests describe the cases that were exercised; functional review considers observed behavior. Independent specialist validation is a separate activity and is claimed only when documented. An automated checker does not itself establish independent professional review.
The public preview includes tests, deterministic fixtures, validation notes, and known issues. The reviewed demonstration changes a resource budget while retaining required digest and byte-count checks.
The relationship between intent, plan, execution, and revision is visible in retained records.
Scope of the claim
Implemented operations are bounded file-audit tasks. Independent validation is pending. Requirement prose is retained for human alignment, not automatically judged. Source is available under PolyForm Noncommercial; commercial use outside its grant needs separate permission.
An annotated source walkthrough
Change the constraint. Keep the required result inspectable.
- Declare the taskThe documented fixture audits three inputs and requires exact file digests and byte counts.
- Revise the resource constraintThe demonstration changes a declared read-buffer budget from 4 MiB to 64 KiB and changes the execution binding.
- Compare the resultCandidate outputs are checked against a separate read path. The paths share the hashing library, so this is not fully independent verification.
This walkthrough describes the published bounded fixture demonstration. It was not rerun for this website release. The resource budget is a technical constraint, not a financial budget or a claim of cash savings. Independent validation remains pending.
Connected practices
A useful next step
Bring the context. Find the next step.
Bring the outcome, the context, and the constraints.
We’ll start by defining a useful next question.
Start a conversation
Request first. Scope and next steps follow review.
Connect the method to your business.
Explore consulting services ↗ · Read the practical guides ↗ · Prepare a discovery brief →