Home

RobotTransformation

RobotTransformation is the product monorepo being established for RX: a vendor-neutral platform connecting heterogeneous robots, equipment, and services through common task, authority, state, result, and recovery contracts.

Current scope: M0–M4 technical gates passed; SDK/distribution verification is in preparation. PR #4 established the full product CI union, and PR #5 established canonical documentation and contract locations. Release, cutover, physical layout and bounded module changes remain separate gates. main is still the source-free bootstrap; the validated integration source is on develop. No physical operating readiness or CP2 acceptance is implied.

Open the delivery project · Milestones · Labels

Start here

Guide	Purpose
Project workflow	How work enters and moves through RobotTransformation — Delivery
Milestones and labels	Migration sequence, priorities, and issue classification
Repository migration	Snapshot import, preserved history, staged cutover, and rollback boundaries
Evidence and acceptance	What a result supports and who may accept it
Architecture map	Core responsibilities, internal dependencies, and SDK surfaces

Sources of authority

Current product documentation and semantic contracts are owned by RobotTransformation. The current documentation index is a navigation link. The following fixed M4 checkpoint identifies the verified source:

• Product definition
• Framework master plan
• Core charter
• Canonical contracts

rx_docs owns evidence and historical documents under its evidence charter. Original document paths, commits, tags, signatures and evidence remain preserved.

This wiki is a navigation and working-policy guide. It is not the normative contract source, a substitute for accepted evidence, or an alternate implementation-status ledger. Issues and the delivery project link to the controlling source and evidence for each item.

Preserved CP2 boundary

The earlier F2′ CP2 precheck and the later rejected acceptance run are different records. The later diagnosis records CP2 NOT ACCEPTED, CP3 NOT STARTED, with the original uncertain operation and resource hold preserved. Its original three documentation commits were published unchanged through rx_docs #118. Publication did not accept or settle the Run. The migration proceeds in parallel without changing that preserved environment. See Evidence and acceptance for the two immutable records and their scope.

Tracking policy

These pages define the initial tracking policy v1. They apply to issue and project organization. Changes to product semantics still require the product contract and review process; a wiki edit cannot approve such a change.