Public release · 31 August 2026

ASF: APTD Sensor Fabric

A provenance-bearing interoperability layer between machine intelligence and observable systems.

Core v0.1: public / frozen
Motorola M0: public / frozen
Read-only observation fabric

Claim boundary: ASF is experimental observational infrastructure. It does not demonstrate a completed physical APTD, machine consciousness, autonomous physical control, production safety, continuous sensing, hardware attestation, or general truth authority.

What ASF is

ASF is an experimental, read-only interoperability fabric for provenance-bearing machine observations. It preserves source, identity, provenance, time, health, sampling semantics, history, and rate limitations before higher layers decide relevance, qualification, formation, or authority.

One interface to observe. No interface to blindly obey.

WORLD
  -> ADAPTER
  -> RECEPTOR EVENT
  -> LEDGER / OBSERVATION FABRIC

Public evidence status

Release	Status	Evidence	Boundary
ASF Core v0.1	FROZEN / LOCALLY VERIFIED / PUBLIC RELEASE	30 tests passed; freeze verification OK; no actuation surface	Read-only core, no Motorola physical witness in this first freeze
ASF Motorola Live Probe M0	FROZEN / LOCALLY VERIFIED / PUBLIC RELEASE	46 tests passed; live Android source; restart, disconnect, tamper, MCP boundary, no device writes, no actuation	Read-only polled ADB telemetry; not hardware-attested or continuous sensing
Physical APTD	NOT DEMONSTRATED BY ASF ALONE	ASF supplies observation infrastructure beneath or alongside APTD	No governed physical execution boundary is released here
Machine consciousness	NOT CLAIMED	No ASF release contains a consciousness claim	Observation interoperability is not sentience, personhood, or AGI
Autonomous physical control	NOT IMPLEMENTED	MCP and HTTP surfaces expose observation/proposal paths only	No `adb_shell`, `device_command`, `execute`, `run_command`, or actuation endpoint

First physical witness

Motorola Live Probe M0 reports the same semantic proposition, battery = 100%, through five causally distinct sources: a live read-only Motorola observation, a test fixture, a simulation, a replay of the live event, and a text claim. ASF preserves distinct event identities and provenance for those sources.

This matters because the same proposition is not the same causal event. In ASF, that is an executable design property demonstrated by the implementation; it is not promoted here to a universal theorem.

Relation to APTD

ASF is observational infrastructure beneath or alongside the APTD architecture. APTD remains the governed transition/execution boundary. Current ASF stops before physical execution authority.

COGNITION
  -> PROPOSAL
  -> GOVERNANCE
  -> APTD
  -> PHYSICAL CONSEQUENCE

Relation to Formation Calculus

ASF supplies instrumentation for testing whether retained distinctions such as same semantic proposition with different provenance or acquisition paths later produce different legitimate downstream transitions. ASF does not prove Formation Calculus.

Known limitations

Motorola observations are polled snapshots.
No claim is made for continuous sensing between polls.
SOURCE_BOUND is transport/adapter binding, not cryptographic hardware attestation.
The raw device serial is not a public identity.
The disconnect test used a host-side invalid binding.
No remote feeds are implemented yet.
No actuation surface exists in this release.
Qualification remains separate and not fully implemented.
TEST_FIXTURE was introduced after v0.1 and does not rewrite the Core v0.1 freeze.

Inspect the release

ASF repository

Public source, docs, tests, protocol schemas, adapters, freeze artifacts, and release tags.

Open GitHub repo

Core v0.1 release

First frozen read-only ASF interoperability core.

Open Core release

Motorola M0 release

First frozen live external physical-source witness using read-only Android/ADB telemetry.

Open M0 release

Roadmap boundary

ConnectorDome is the planned open ecosystem for discovering, building, validating, and sharing ASF-compatible connectors. ConnectorDome v0.1 is not published in this release. ExoMCP remains a separate security project and is unchanged by this tranche.