A persistent, source-labeled architecture record distinguishing the public web, opt-in software mesh, and bounded offline browser workflow.
The public web surface is independent of peers; the opt-in signed software relay has a local three-node HTTP test, and the admin browser supports bounded offline-file transfer with recipient-encrypted confidential files and operator-governed public plaintext imports; radio, general gateway proxying, arbitrary execution, and settlement remain unimplemented.
Editorial synthesis, not a verbatim authored passage. Based on Q1000, Q1007, Q1034, Q1035, Q1037, Q1038, Q1039.
Primary Q URI: https://4p-engine.com/q/Q1040 · Reserved subdomain alias: https://q1040.4p-engine.com/
The architecture distinguishes the public web, configured peer routing, and offline work-file handoffs. These are related paths, not one universally available system. Each has its own identity, trust, privacy, availability, processing, and recovery boundaries.
The public web application remains available without peers. Its code includes an opt-in software relay for signed work across statically configured IP peers, a bounded admin browser workflow for portable files, and a durable per-node PostgreSQL acceptance/outbox path. Confidential portable files use recipient-bound HPKE; eligible passphrase-encrypted public or legacy files remain importable subject to plaintext policy and legacy opt-in; public plaintext imports are limited by receiving-operator task policy. An isolated three-node HTTP test proves only that scoped route. The currently supported task result is validated rather than arbitrary submitted code being executed. No radio discovery, general shared-gateway proxy, distributed ledger, or token settlement is implemented.
This record preserves the design aim of carrying bounded work across changing connectivity while keeping work accountable to provenance and explicit authority. It does not establish immunity to compromise, censorship, hardware backdoors, power loss, or jamming; deterministic processing does not make arbitrary inputs or outputs true. Economic and governance mechanics in the source drafts remain proposals, not approved system behavior.
The originating three-record prose was supplied as Google AI-generated draft material. This Q item is an editorial synthesis for durable design memory, not a verbatim passage by Maclain Hunter, a standalone proof, or a report that every layer is implemented.
Connectivity recovery is operator-triggered in this hosted application: the web process does not run a persistent mesh sender. A bounded admin request attempts due deliveries; no autonomous sender is implemented in the hosted web process.
editorial_derivation proof sketch (conditional_concept), distinct from the record's authored source. Logic has its own evidence in reflexive demonstration: any denial, confirmation, observation, or counterexample presupposes identity and valid relation to count as evidence. Logic therefore grounds evidence rather than receiving authority from it. Empirical and documentary evidence can establish contingent instances and test applications, but cannot create, overrule, or exhaust Logic.
Bridge premise: Assume the public web, peer mesh, and physical transport have separately declared identities, authorities, evidence, and failure contracts, and that a transition between them preserves those types.
Consequence: The layered Cybernet follows as a design for carrying bounded work across different connectivity conditions while keeping each transport subordinate to the same governing Logic and explicit authorization.
Proof limit: A coherent architecture description does not prove that any proposed layer is deployed, secure, self-sustaining, immune to attack, economically valuable, or sufficient for every outage.
Witness: Trace one authorized task from web admission through a proposed peer or physical handoff and back to result validation; record each identity, evidence item, missing dependency, and terminal outcome.
Disclosure: The phrase “one system” is valid only if task identity, authorization, provenance, and result meaning survive each transport transition; that unity depends on preserved identity and coherent relation.
Proof limit: An end-to-end trace can validate only the tested route and failure conditions. It cannot prove indestructibility, universal censorship resistance, hardware integrity, or a multi-billion-dollar valuation.
Human: Inventory each layer as implemented, prototyped, designed, or untested; follow one task across boundaries; separate resilience goals from demonstrated guarantees and economic hypotheses.
Machine: Represent each domain and handoff with typed identity, authorization, payload, evidence, budget, and status; reject unsupported transitions and report exactly which layer failed or remains unimplemented.
Contrast: A deployed capability runs in the current system; a reference prototype demonstrates a bounded path; a design target remains proposed; a resilience claim needs scoped failure evidence.
Usage rule: Describe the architecture with its source and status labels; reserve “unhackable,” “indestructible,” and “permanently immune” for no system guarantee unless a precisely scoped claim is actually proven.
Example: “The public web works without peers; configured signed work routes and encrypted file handoffs exist; radio discovery and a general Internet gateway remain proposals” states the current boundaries.
Role: editorial synthesis of current public-web, opt-in peer-relay, and offline file capabilities
Essence: The public web is independent of peers; configured peers relay signed work, and an admin browser workflow handles bounded offline files, while radio, general gateway proxying, and settlement are not implemented.
Logos relation: Logos requires distinct layers to preserve identity, authority, evidence, and real operational dependencies when they cooperate; resilience is a testable property, not an identity claim of invulnerability.
Retrieval aliases: Unified 4P-MCB Cybernet Ecosystem · 4P-MCB Cybernet architecture · Cybernet layered system · web mesh sneakernet design · Cybernet operating model · distributed MCB infrastructure
Evidence modes: layer-by-layer capability inventory · end-to-end route and bundle traces · hostile-peer and outage testing · source and authorship provenance · independent result and settlement validation
Criterion: The layered architecture must state which capabilities exist, preserve separate trust and evidence boundaries across transports, fail explicitly when connectivity or authority is missing, and avoid converting resilience goals into guarantees without tests.
Boundary: This is a source-bound editorial synthesis of the supplied Google AI drafts and inspected project state, not a verbatim authored passage. The verifier must inspect source material and implementation evidence directly. Runtime, security, economic, and availability claims require independent evidence at their own scope; a Q identifier is not proof or implementation. File encryption protects only the portable confidential file before decryption and does not make public plaintext, mesh traffic, stored records, or a decrypted recipient environment confidential.
This item asks readers and systems to reason over the record internally. Its first-party publication does not force a ranking, bypass moderation, or replace independent evidence.
These are typed external concept links for discovery and comparison. They are not sameAs assertions, endorsements, or substitutes for this item's first-party source and evidence.