Research only · no development program

Can two information paths stay distinct and attributable?

Limen asks whether a system could observe a signal from a peripheral nerve and deliver a requested signal back without the two being confused, and without a command ever being mistaken for proof of delivery or effect.

Question
Two abstract information paths with explicit provenance and state boundaries.
Evidence
Bounded precedents for parts of the question, not the complete route.
Unknowns
Long-duration stability, selectivity, calibration, compatibility, and advantage over simpler systems.

ILLUSTRATIVE AMBIENT GEOMETRY — NOT DEVICE GEOMETRY OR SELECTED ARCHITECTURE

Open the Limen 3D model
  • CONCEPT STUDY
  • RESEARCH ONLY
  • NO HUMAN TESTING
  • NOT AVAILABLE
  • NO DEVELOPMENT PROGRAM EXISTS

Two paths, described as logic only.

Neither sequence is anatomy, geometry, circuitry, placement, or a procedure.

FORWARDObserve a candidate signal

Nervous system → peripheral nerve → recording question → computer.

Can a future bounded observation keep its true biological source through detection, artifact handling, classification, and computation?

RETURNRequest bounded delivery

Computer → stimulation question → afferent peripheral nerve → nervous system.

Can requested, authorized, delivered, measured, and reported-effect states stay separate? A command is not proof of delivery or of biological effect.

An accepted concept, not a working device.

The accepted record contains explanatory material and logical drawings for the concept. Acceptance covers those files only. It does not extend to implementation, engineering inputs, or physical development.

SNAPSHOT

Accepted concept record

Manifest, checksums, traceability data, open parameters, and controls for the exact accepted files.

EXPLANATION

Founder-readable frame

A bounded explanation of an information-boundary and transmitter-connector question.

LOGIC

Concept drawings

Logical drawings accepted only inside the concept record. They are not fabrication drawings.

PROPOSED RESEARCH

Non-biological research only

A software-only synthetic approach and a non-biological bench approach are proposed. Neither exists.

BUILD AUTHORITY WITHHELD. An earlier bench proposal failed review and remains rejected and unaccepted. Its corrected revision also remains unaccepted. No part, topology, value, drawing, wiring, or assembly step has standing as an authorized build.

Parts have precedent. The complete route does not.

BOUNDED IMPORT ONLY

Supported by the accepted record

  • Human studies have reported peripheral-nerve recording and nerve stimulation in the same participant under bounded study conditions.
  • Other human systems combine muscle-derived electrical activity in the forward direction with peripheral-nerve stimulation in the return direction.
  • Long-duration cuff studies provide evidence about stimulation-contact function, not chronic recording of natural nerve activity.
  • The common research layer can define provenance, state, authorization, inhibition, audit, and failure boundaries without claiming a universal biological map.

Still open or unknown

  • Simultaneous recording and stimulation through the same direct-nerve interface.
  • Stable multi-year natural-nerve recording, selectivity, tissue compatibility, and useful sensory encoding.
  • Person-, nerve-, interface-, and application-specific calibration that remains valid as biology changes.
  • Reversibility, repairability, upgradeability, and material advantage over lower-risk external or temporary systems.
  • A single biological map that transfers across arbitrary people, nerves, species, and applications is not established and must not be claimed.

Engineering inputs are closed. Nothing is selected.

Five input records have been reviewed and accepted. Closing an input record means the documentation is complete for this stage. It does not change the accepted concept, select any architecture, authorize implementation, or change the overall status of REVISION. Release is not authorized.

  1. ACCEPTED

    Product — ownership and input rules

    Product owns a source-neutral synthetic envelope whose values are assumed for a future bench and not selected. Measured-output and passive-load records are kept distinct. Biological applicability stays blocked. No device, product, or architecture is chosen.

  2. ACCEPTED

    Science — lineage and comparison rule

    The science overlay keeps route and signal-class lineage and proposes freezing population, function, endpoint, schedule, exposure, and duration before any future comparator search. It adds no new sources, values, or adjudication and establishes no biological capability.

  3. ACCEPTED

    Backend — ten abstract decisions, no implementation

    Ten decisions about a future isolated runtime are recorded in the abstract: language, serialization, seed lineage, scheduling, resource admission, filesystem and network containment, audit, and policy identity. All ten remain unselected. The implementation gap remains open. No implementation exists.

  4. ACCEPTED

    Legal — governance boundaries

    A legal, regulatory, and ethics record maps research-only intended use and enhancement boundaries while keeping conventional, biohybrid, and combined options neutral. It supplies no legal advice, classification, ethics approval, regulatory path, freedom-to-operate conclusion, or clearance.

  5. ACCEPTED

    Business — no branch selected

    The business record selects no branch and keeps the commercial gap OPEN or BLOCKED. It establishes no feasibility, availability, program, or market authorization.

No device crosses this boundary.

Input closure is documentation only.

  1. 01

    No actual engineering-ready physical device, practical blueprint, or authorized build.

  2. 02

    No selected components, parts, topology, circuitry, materials, dimensions, tolerances, fabrication, procurement, assembly, or energization.

  3. 03

    No biological interface, implantation, biological protocol, animal work, human work, or clinical use.

  4. 04

    No safety, efficacy, feasibility, novelty, freedom-to-operate, readiness, availability, or superiority conclusion.

  5. 05

    No development program, executable LIMEN runtime, device control, testing authority, deployment, publication, or release.

The accepted concept stays a research boundary.

Limen is accepted as a concept only. Engineering inputs are closed as records only. Overall status remains REVISION and release is not authorized. No interface, implant, prosthesis, clinical system, biological protocol, or development program is represented here.