Frankenstein Engine

A local-first controlled automation engine built around execution-safety gates, wallet policy, simulation, reconciliation, and operator approval.

What it does

State inspection before motion.

Market data inspection

Risk review

Strategy evaluation

Transaction simulation

Wallet activity inspection

Reconciliation

Kill switch state

Explicit operator approval

What remains private

Public clarity without operational exposure.

Rust source code

Private strategy logic

Wallet and security internals

Provider configuration

Execution authority

Operational credentials

Local file paths

Public architecture

A deliberate boundary between signal and authority.

Layer 01

Website public surface

Public pages explain the safety posture, logbook, access flow, and architecture language.

Layer 02

Redacted status and documentation

Only polished public context is surfaced. Sensitive wallet, provider, and execution-safety details stay out of the site.

Layer 03

Private backend boundary

The backend controls what the public surface can see and keeps protected mechanics behind the operating boundary.

Layer 04

Frankenstein Engine

The Engine evaluates state, checks policy, runs simulations, reconciles exposure, and refuses unsafe action.

Layer 05

Local wallet and safety gates

Sensitive action remains gated by wallet policy, simulation, reconciliation, kill switch state, and operator approval.

Safety boundaries

Research can propose. It cannot command.

Execution remains blocked when market data is incomplete, simulation fails, wallet activity is unknown, positions do not reconcile, the kill switch is active, configuration drifts, or operator approval is missing.

Market data is incomplete
Transaction simulation fails
Wallet activity is unknown
Positions do not reconcile
The kill switch is active
Configuration drifts from policy
Operator approval is missing

LLM role

Advisor and explanation surface.

The LLM layer is an advisor and explanation surface, not execution authority. It cannot bypass the Rust safety engine, wallet policy, simulation requirements, reconciliation checks, kill switch state, or operator approval.

Current public status

Internal controlled safety cycle closed. Entry and exit review completed as a safety record. Wallet activity verified. Reconciliation clean. No remaining exposure is surfaced as public product readiness. Any new action remains gated by fresh preflight and explicit operator approval.

Operator access

The public surface stays bounded.

Access requests enter review. Operator access currently means private preview review, not trading permission. Approval does not imply custody, wallet control, execution, or permission to bypass the protocol.

Request Operator Access