Neurobrick is independently developed financial research and execution infrastructure designed for proprietary capital management.
NeuroPublic integrates research, market access and bounded execution authority. KR Rotation owns a scheduled KIS equity lane; NeuroForAll separates account-scoped workers. Control Plane supplies shared coordination and market services. The stack includes order recovery, fill-ledger inspection, lot accounting and operational evidence.
Reviewed execution paths span domestic and overseas equities, cryptocurrency spot, perpetual futures and options, and domestic and overseas futures and options. The applicable engine, broker, product permissions and operating configuration determine live use.
Neurobrick is independently architected, developed, maintained and operated by a single individual. Ownership and operating model →
The infrastructure is operated solely with assets owned by its individual developer and operator. It does not accept external investor capital or solicit third-party investment.
Research, data readiness and market execution share an environment while retaining separate admission and authority checks. KIS equity consumers, Binance exchange consumers and a separate Alpaca option branch provide distinct routes for domestic and US equities, cryptocurrency spot, perpetual futures and options, and US equity options.
Operator responsibility: Own research-input readiness, KIS envelope checks, exchange-specific permissions and submission identity; preserve transaction references across the fill and lot-accounting boundary.
KR Rotation
Independent domestic equity rotation
A dedicated domestic stock and ETF rotation engine owns its schedule, account context and KIS cash-order lane. Its arm condition, admission lease and submission journal make permission and order intent explicit within that lane.
Operator responsibility: Own the rotation schedule and account boundary, arm and lease conditions, and the journal that records cash-order submissions.
NeuroForAll
Account-scoped execution engine
Domestic and overseas equity workers carry account context through permission checks, submission recording and reconciliation. The reviewed implementation separates the account boundary from shared research and workflow infrastructure.
Operator responsibility: Own worker-to-account binding, live-permission checks, recorded submissions and reconciliation interfaces.
Control Plane
Coordination and shared market access
Shared services supply health and evidence views, portfolio controls, release coordination and market-specific broker or exchange access. Its integrations cover cryptocurrencies, domestic and overseas equities, and domestic and overseas futures and options. Order admission remains with each consuming execution path; Control Plane is not a fourth independent engine or a universal order gate.
Operator responsibility: Own the meaning of health and evidence projections, portfolio protection and release coordination; keep those services distinct from engine-local order permission.
Engineering the boundary between intent and action.
These implementations address concrete failure modes: delegated permission escaping its bounds, a restarted process losing an order attempt, shared state changing implicitly, and a research result losing its input identity.
Owner-bounded authority reaches the executor
Owner-signed delegation sets the boundary for child envelopes. The selected KIS executor consumes precheck and final authorization, including shared usage bounds.
Delegation remains bounded at the point that consumes it, rather than being inferred from the research decision.
Reviewed path: load_delegation / child_outside / delegation_usage in kis_capital_delegation.py; precheck / authorize in kis_capital_envelope_gate.py.
The operator defines the delegation and usage bounds; the executor validates the child authority before the selected submission path proceeds.
Selected KIS source path · opt-in; current activation outside this record
Full scope and source records
The selected KIS gate validates child envelopes against an owner-signed delegation and shared usage bounds while retaining the existing permission-consuming caller.
New source integration. Opt-in; present activation and a live allowed/refused pair remain unverified.
Selected futures close callers persist the attempt before dispatch and resume that same identity after restart. Conflicting or unconfirmed outcomes remain pending.
Recovery preserves submission uncertainty instead of converting a restarted process into a fresh order attempt.
Reviewed path: close_leg / persist_positions in _live_close.py.
The operator owns resolution of ambiguous submissions; the implementation supplies the saved identity and pending state needed for that decision.
Selected futures callers · isolated fake-broker and process fixtures
Full scope and source records
Selected futures callers save an attempt before dispatch, follow its identity after restart and keep uncertain outcomes pending.
Newly reviewed merged recovery change with isolated fake-broker/process fixtures; no new live or unconditional exactly-once claim.
Shared protection state has an explicit migration path
Selected SDK readers and writers consume an optional common state context. Path selection, compatible writes and contextual observations coexist with legacy defaults.
The migration boundary is the consumer that selects the state path, not the presence of a shared directory.
Reviewed path: state_path / atomic_text / publish in sdk_context.py; _ban_file / note_ban in _ban_state.py.
The operator selects which consumers use the context and owns their migration boundary; source integration alone does not establish fleet adoption.
Selected SDK consumers · source-reviewed migration; fleet adoption is separate
Full scope and source records
Selected SDK consumers use a common optional state context and contextual observations without treating migration support as operating adoption.
Newly integrated source path. Running-consumer bindings and fleet-wide adoption are not established.
Operating records retain their own completion and scope
Committed markers retain scan-phase completion. Deployment records identify source and probe observations; recovery records retain the measured case population.
Reviewed path: Prior completed run marker in run-marker-prev.json; Run marker flags in run-marker.json.
The operator interprets each record against its time and population. A completed observer cannot stand in for a recovered financial component.
Dated committed observer records · recovery sample: zero cases
Full scope and source records
Committed scan markers distinguish a completed prior run from an unfinished later scan. Deployment and recovery observer records keep their own source and population.
Newly inspected dated records, not new proof that every guard is active. The recovery population remains zero.
fleet-brain:completed-marker mxroach/fleet-brain · 4392cc595651817149cf3c8fdf74693c059a9d09 state/run-marker-prev.json · Prior completed run marker Source reviewed: 2026-11-01T09:50:03.074Z Recorded run date: 2026-11-01 Source or original-record SHA-256 c1231ece6cbdf077b30eda6aab51d8c8d40f96d40850daf48c2169a4cdb60557
Selected recorded fields: {"run_date":"2026-11-01","completed_at":"2026-10-31T23:25:28Z","phase1_done":true,"phase2_done":true}
fleet-brain:early-scan mxroach/fleet-brain · 4392cc595651817149cf3c8fdf74693c059a9d09 state/run-marker.json · Run marker flags Source reviewed: 2026-11-01T09:50:03.074Z Recorded run date: 2026-11-01 Source or original-record SHA-256 d5b91df08c35c7dfe8f5d038a8305eeda66fa65335a08ef1aa5611127f6f0acf
Selected recorded fields: {"run_date":"2026-11-01","started_at":"2026-11-01T09:00:08Z","phase1_done":false,"phase2_done":false}
fleet-brain:deploy-record mxroach/fleet-brain · 4392cc595651817149cf3c8fdf74693c059a9d09 state/deploy-verification.json · Recorded deployment observer snapshot Source reviewed: 2026-11-01T09:50:03.074Z Recorded run date: 2026-11-01 Source or original-record SHA-256 2356f906b6a9a7d1245f8ae6c4f8650f80ceb395a26cb9c707ada8843bc0b419
Selected recorded fields: {"observed_at":"2026-11-01T09:12:02Z","probe_ok":true,"reported_checkout":"d04ace2fad340cf336500adfb49077f25c4b8237","error_count":0}
fleet-brain:recovery-record mxroach/fleet-brain · 4392cc595651817149cf3c8fdf74693c059a9d09 state/recovery-verification.json · Recorded recovery observer population Source reviewed: 2026-11-01T09:50:03.074Z Recorded run date: 2026-11-01 Source or original-record SHA-256 67074cdf49deb255f28023416beec3de3c34bd78b4cf6994e5aa59c2140a2bd8
Selected recorded fields: {"run_date":"2026-11-01","probe_ok":true,"recovery_cases":0}
The examples are supported by source review, isolated fixtures or dated observations. Live use follows the named engine and its permissions; the source record identifies the coverage of each example.
The public operating material contains two inspectable populations: identified server-side refusals and retained scan markers across repeated runs. The original path, dates and measured scope accompany each result.
The refusal evidence identifies attempted orders and the server-side checks that rejected them. The marker sample records repeated observation-pipeline progression, including partial completion. Together they document different operating responsibilities; neither is a measure of trading success.
Server-side checks refused identified orders.
The original inspection records identified order attempts refused by the server-side risk check and the core sell block.
Recorded execution context · event window 26 September (KST). This is the refused side of the path; a current allowed/refused pair is a separate operating record.
12 retained marker snapshots span 6 run dates, 27 October–1 November. 11 carry both completion flags; 1 retains partial progress. The public fields of every selected snapshot are available for inspection.
Observation-pipeline records · a file-history sample of recorded progress, rather than a service-availability or trading-success rate.
Authority, context and evidence are separate contracts.
01
A proposal carries information. Authority carries permission.
Inference supplies a candidate. Its score does not authorize an action. Permission is evaluated in the engine and context that consume it.
02
Shared infrastructure has a bounded role.
Research, inference and fleet tooling support several systems. Execution context and permission remain inside the relevant engine boundary.
03
Evidence has an identity and a scope.
A result retains its input, source revision, test population and observation window. Local behavior, installed code and natural operating effect are measured separately.
These principles guide the implementation. Component records connect them to the relevant engine paths and source revisions.
Architecture responsibilities
Separate the decision, the permission and the receipt.
01
Research
Inputs retain source, observation time and applicability.
02
Evaluation
A fixed candidate is evaluated against a declared policy.
03
Authority
Permission has an owner, scope and consuming boundary.
04
Execution
An engine acts inside its own execution context.
05
Observation
Time, completion and evidence quality stay attached to each operating observation.
06
Receipts
Results retain identity, source and the measured population.
The responsibilities are shared across the architecture; the execution-chain map shows the reviewed connections and their engine-specific context.
Implementation and dated observations
Controls have observable behavior.
The public records contain specific control states, refused order attempts and guarded submission paths alongside scoped local engineering tests. Each observation keeps its original environment and date.
Portfolio kill-switch state
The inspection reported the portfolio kill switch as ARMED, separately from the approval-axis summary.
Recorded scope: ARMED is a reported configuration state. This record does not demonstrate a triggered portfolio stop, its reach across every order path, or the current state.
The original inspection records identified order attempts refused by the server-side risk check and the core sell block.
Recorded scope: This is an internal dated observation on a particular execution context. The executing commit was not recorded; accepted-case testing, universal enforcement and present operating state are not established by it.
Record observed/reviewed ·
Event window stated in the original: 26 September (KST)
Every autonomous submission attempt in the stated half-hour was skipped while opt-in, admission-lease and certified-trial conditions were inactive or not ready.
Recorded scope: This records refused or skipped progression, not successful issuance, certification or release. Development/testnet observations elsewhere refer to another service and must not be read as this same path changing over time.
Follow each link for the original evidence scope, source references and integrity checks.
Public scope
Architecture, authority and technical evidence.
Public material covers system architecture, authority boundaries and scoped technical evidence. Returns, balances and proprietary strategy parameters remain private.