Renigma
Preserve what matters. Inspect what changes.
A workbench connecting language, context, operations, scenarios, evidence, and human control.
Explore the project studyZen Jones / Blake · AI-assisted systems solutions & integrations consulting
Make your business systems
work together.
I use agentic AI and structured development workflows to help clarify business processes, connect information and develop practical tools and integrations. Start with one process, a defined scope and clear ways to check the result.
The opportunity often sits between things: a customer’s request and a team’s workflow, scattered information and a decision, an ambitious idea and a practical first step.
AI-assisted delivery, shaped around the work.
AI supports how I develop a solution. Depending on the problem, the result may be a better-configured tool, an integration, a dashboard or a custom workflow. It does not necessarily need AI to operate.
INDEPENDENT PROJECTS ACROSSFractalDesignZ ↗+ZuluYokohama ↗Ideas developed through practical exploration.
01 / The opportunity between layers
Make the handoffs
make sense.
Good ideas lose momentum when people, information, and systems stop sharing the same context.
Breaking down a boundary starts with understanding it: what each side knows, what must pass between them, and what needs to stay true. That understanding can reveal a better interface, a clearer process, or an opportunity worth testing.
Explore the framework ↗02 / From intent to evidence
A pattern becomes valuable
when it does useful work.
Clarify the meaning. Connect the parts.
Build, check, and refine the process.
FIRST, UNDERSTAND THE SEPARATION
Different teams. Different views.
A customer request, an operations record, and a delivery decision each carry part of the story. The boundary is where context can be lost.
Illustrative business workflow. Select a stage to explore the method; this is not a simulation or a project performance result.
03 / Independent projects
Ideas with a
working form.
Explore all seven projects ↗DOAPO
Public records. A usable decision context.
An explorer for North Dakota permit, spud, and well-status records with explicit decision boundaries.
Explore the project studyCharger Services
Technical expertise, clearly communicated.
A service website connecting commercial explanations, technical knowledge, research experiences, and reviewable briefs.
Explore the project study04 / Find your way into the work
Different perspectives.
A shared direction.
01 / YOUR PERSPECTIVE
Business & product teams
Between business intent and the tools used to carry it out.
Explore this perspective ↗02 / YOUR PERSPECTIVEPartners & investors
Between the promise of an idea and a testable opportunity.
Explore this perspective ↗03 / YOUR PERSPECTIVETechnical collaboration
Between an architectural concept and the details that make it work.
Explore this perspective ↗05 / Capabilities with context
What we can
work on together.
Each direction connects to actual work.
The right scope starts with your situation.
CAPABILITY
Requirements & system design
Turn an ambiguous objective into explicit relationships, constraints, and acceptance conditions.
CAPABILITY
Operational tools & interfaces
Connect domain information to a usable workflow and a decision someone needs to make.
CAPABILITY
Evaluation & analytical tools
Make calculations, assumptions, and the evidence behind a result open to inspection.
CAPABILITY
Research & computational experiments
Give a promising pattern a bounded experiment, a comparison, and a useful next question.
Practical ways to work together
Find your first improvement.
Workflow automation ↗
Requests lose their owner between steps.
A useful first scope
Map one recurring process, identify its exceptions, and prototype one repeatable step with a human review point. Establish a baseline before deciding what to automate.
Relevant evidence
Mission Lab shows bounded execution and revision; DOAPO separates a proposal from authorization.
Custom business tools and dashboards ↗
The team cannot trace a report back to a trusted record.
A useful first scope
Choose one decision and a representative dataset. Build a reviewable view that exposes definitions, source context and the next action before expanding to more users or data.
Relevant evidence
DOAPO organizes records for review; Horizon RWT exposes data mapping and analytical checks.
Systems integration and modernization ↗
Useful tools disagree or stop sharing context.
A useful first scope
Review one boundary between systems: what information crosses it, which source owns each value and what happens when an update fails. Test an incremental path before proposing a replacement.
Relevant evidence
Horizon RWT demonstrates imported-data handling; Renigma provides structured modeling perspectives. These are related capabilities, not proof of a deployed business integration.
A useful next step
What needs to work better?
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.
See intent become action.
Explore a fictional customer request, missing information and a changed requirement. See why current approval and passing checks matter.
Try the request-to-delivery demonstration →Start with the challenge. Connect the capabilities.
Unclear requests, scattered information, lost ownership and changing requirements each call for a different combination of practices. See how the body of work informs a bounded next step.
Explore the framework through business challenges →