Archive reading context · not a source record
Limen Concept V1 blueprints — accepted as concept communication only
CONCEPT STUDY · RESEARCH ONLY · NO HUMAN TESTING · NOT AVAILABLE · NO DEVELOPMENT PROGRAM EXISTS
The current custody status is ACCEPTED_CONCEPT_COMMUNICATION_ONLY. The exact eight-page PDF was accepted as a truthful, deterministic concept-communication snapshot. It is not a physical blueprint, a selected artificial-hand target, or a selected architecture.
ACCEPTED_CONCEPT_COMMUNICATION_ONLY · EXACT PRODUCT CONCEPT SNAPSHOT ONLY
- Integrator decision
- ACCEPTED — EXACT PRODUCT CONCEPT SNAPSHOT ONLY
- Git state
- UNTRACKED_PENDING_NB-LAND-004
- Product use
- Concept-communication structure only
- Release
- Unauthorized
What this artifact was for
The package gives Product Design a source-bounded way to explain how Limen could be investigated. It uses bidirectional artificial-hand control and sensory return as a research frame: information moving toward a controller is kept distinct from information proposed for a return path.
That frame routes questions. It does not choose a clinical indication, assert biological capability, or turn a generalized ambition into a device design.
What the eight sheets contain
- System and route boundaries — BP-01 to BP-03
- A whole-system concept map, a forward control-intent research chain, and a return sensory-information chain. The drawings separate logical stages, authority, inhibit handling, and post-delivery records.
- Control and lifecycle questions — BP-04 to BP-06
- A state-and-failure machine, the boundary between common platform functions and person-specific mapping, and a maintenance, replacement, upgrade, rollback, and revalidation sequence.
- Evidence classes and future bench abstraction — BP-07 to BP-08
- A comparison that keeps direct nerve recording, muscle-derived recording, and combined evidence classes distinct, followed by an abstract software-only R0 and non-biological R1 research-bench view. R0 means an offline synthetic software stage; R1 means a possible later non-biological bench stage.
This page deliberately does not reproduce the drawings. The source PDF remains the record for exact sheet content.
Why its authority is narrow
The frozen README, manifest, and sheets retain the earlier words CORRECTED PRODUCER CANDIDATE — PENDING FRESH INDEPENDENT QA AND INTEGRATOR ACCEPTANCE. Those accepted bytes were not rewritten after review. The later Integrator record and HANDOFF.md §25 are the post-acceptance authority for the exact hash set.
That acceptance establishes only internal consistency, deterministic reproduction, visual readability, and truthful evidence limits for a concept-architecture communication package. The later Step 5 input register further limits reuse to concept-communication structure; its artificial-hand frame is not an accepted Step 5 target.
What it cannot establish
- No physical, fabrication, implantation, surgical, anatomical, or clinical blueprint.
- No selected target, architecture, interface, electrode, component, circuit, connector, material, dimension, tolerance, placement, power path, or communication method.
- No biological detection, stable neural decoding, useful sensory encoding, chronic stability, safety, efficacy, feasibility, novelty, freedom-to-operate, regulatory-readiness, or availability conclusion.
- No R0 or R1 implementation, procurement, assembly, bench execution, biological work, deployment, publication, or release authority.
Page coordinates are presentation coordinates only. Lines describe logical information or control relationships; they are not anatomy, wiring, circuitry, or surgical paths.
How to use this archive page
Use this page to understand the drawing set’s status and reading order before opening the PDF. Use the PDF when exact labels, sheet relationships, or source-adjacent caveats matter. Do not cite this page as evidence for a scientific, engineering, legal, product, QA, acceptance, or release conclusion.
Source identity and controlling records
Source PDF: docs/design-comps/limen/CONCEPT_V1/LIMEN_CONCEPT_V1_BLUEPRINTS.pdfPrivate repository source
SHA-256: 6bd036e9b093c7a9582f3b02e1d9a769e42ef3e3f387ec2d4b0922405b5afa71
Accepted package controls: manifest 769c2d5cdc8398b841d307b275ab728f9d3518f60bfc1da7c53550ff1b55048c; checksum registry bda9fa025f0d824163182fdeefe8542cf73b5a1e4d596581c84a67caa43e8317; ordered 31-path digest 9a1e3185813efdd15a4af787aa4bf6e79ebd9b46fc2551e816c2f535feccfc85.
- HANDOFF.md §25
- Post-QA acceptance authority for the exact Step 3 R2 bytes and the controlling scope limits.
- 02-integrator-acceptance.md
- Decision
ACCEPTED — EXACT PRODUCT CONCEPT SNAPSHOT ONLY, exact hashes, observed controls, and explicit non-authorizations. - orchestration/LIMEN_SPLIT_MANIFEST.tsv
- Current custody status
ACCEPTED_CONCEPT_COMMUNICATION_ONLYand Git stateUNTRACKED_PENDING_NB-LAND-004. - CONCEPT_V1/README.md and ARTIFACT_MANIFEST.md
- Frozen producer-time purpose, drawing semantics, non-goals, inventory, and PDF identity.
- STEP5_PRODUCT_FRAME_R2/README.md
- Accepted-input register limiting Concept V1 to concept-communication structure and rejecting target selection by implication.