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 focus: DRAFT-M0–M1 product delivery. The approved source-home cutover is complete; product source is on both main and develop. SDK/distribution verification remains unresolved and continues as #12; the old PR #6 is parked. CP2 remains unaccepted. Historical milestone closure does not change those outcomes.

Start with the product goal and agile roadmap, goal #25 and current Sprint. Product milestones M0–M7 are distinct from historical MIG milestones. The roadmap records Now/Next/Later, entry/exit criteria, dependencies and review cadence.

Open the sprint project · Milestones · Labels

Start here

Guide	Purpose
Project workflow	How work enters and moves through RobotTransformation — Sprints
Milestones and labels	Product outcomes, migration disposition, 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.