Operator control before automation.

Frankenstein Protocol™ is under construction. This page states the security philosophy guiding the public build; it does not claim a completed production system, public user-money readiness, or autonomous trading authority.

Human override

Critical workflow boundaries should have a human stop path. The public project language treats override as part of the architecture, not as a fallback slogan.

Scoped access

Access should be narrow, intentional, and revocable. Broad permissions and invisible handoffs are outside the operating model being described here.

Audit trails

Runs should leave reviewable traces: approvals, exceptions, outputs, and intervention points that can be inspected after activation.

Simulation before sensitive action

Transaction paths should be simulated before any sensitive boundary. Failed simulation remains a stop condition.

Reconciliation after action

Wallet activity, local state, and remaining exposure should be inspected after controlled cycles so mismatches are handled before forward motion.

Observable run state

Machine state should remain visible enough for an operator to understand what is happening, where the boundary sits, and when escalation is required.

Advisor, not authority

LLM-assisted research may propose or summarize, but it cannot override risk checks, wallet policy, kill switch state, simulation, reconciliation, or execution-safety gates.

Refusal posture

Incomplete market data, unknown wallet activity, active kill switch state, position mismatch, missing operator approval, or unsafe configuration should stop the workflow.

No opaque automation

The security posture rejects black-box automation theater. Rules, limits, and review paths matter more than claims of autonomy.

010

No official token or cryptocurrency

Frankenstein Protocol™ has no official token or cryptocurrency. The public website is not a token sale, exchange, broker, custody service, or investment product.