@cuylabs/physical-core 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
package/README.md ADDED
@@ -0,0 +1,78 @@
1
+ # @cuylabs/physical-core
2
+
3
+ Agent-agnostic physical AI contracts.
4
+
5
+ This package defines shared TypeScript shapes for physical sessions,
6
+ observations, artifacts, capabilities, safety policy, execution traces, and
7
+ task outcomes. It does not depend on an agent runtime.
8
+
9
+ It is intentionally backend-neutral. It gives applications a common vocabulary
10
+ for simulator and hardware sessions while backend packages connect those
11
+ contracts to concrete robotics frameworks, runtime services, middleware, and
12
+ hardware stacks.
13
+
14
+ `@cuylabs/physical-core` is not a robotics runtime and it is not a replacement
15
+ for a backend's native environment. It defines the common contract for
16
+ observing a physical session, inspecting artifacts, describing capabilities,
17
+ capturing execution traces, and carrying safety metadata across higher-level
18
+ agent or workflow systems.
19
+
20
+ ## Install
21
+
22
+ ```bash
23
+ npm install @cuylabs/physical-core
24
+ ```
25
+
26
+ ## Use
27
+
28
+ ```typescript
29
+ import type { PhysicalSession } from "@cuylabs/physical-core";
30
+
31
+ const session: PhysicalSession = await createYourPhysicalSession();
32
+ const state = await session.getState();
33
+ ```
34
+
35
+ ## Package Boundary
36
+
37
+ Use this package when you need:
38
+
39
+ - a common `PhysicalSession` interface for simulator and hardware backends
40
+ - typed observations, artifacts, execution traces, and task outcomes
41
+ - safety metadata that can be consumed by host applications, approval systems,
42
+ and UIs
43
+ - backend-neutral contracts that do not depend on any agent runtime
44
+
45
+ Do not put backend-specific launchers, prompts, simulators, perception models,
46
+ robot APIs, or model-facing tools here. Those belong in runtime packages such
47
+ as `@cuylabs/physical-capx` or binding packages such as
48
+ `@cuylabs/physical-agent-core`.
49
+
50
+ ## Mental Model
51
+
52
+ A physical integration has three layers:
53
+
54
+ 1. The host or agent harness decides what to do next.
55
+ 2. The physical adapter translates shared session calls into a concrete
56
+ robotics backend.
57
+ 3. The robotics backend owns the simulator, robot, sensors, task state, and
58
+ low-level execution.
59
+
60
+ `@cuylabs/physical-core` is the middle contract. It makes physical state and
61
+ side-effecting actions legible to higher-level software without forcing every
62
+ robotics backend to expose the same native APIs.
63
+
64
+ ## Boundary
65
+
66
+ This package owns reusable physical AI vocabulary. Agent-runtime tools belong in
67
+ binding packages such as `@cuylabs/physical-agent-core`. Backend-specific
68
+ runtime clients belong in packages such as `@cuylabs/physical-capx`.
69
+
70
+ ## Docs
71
+
72
+ - [docs/README.md](./docs/README.md) for the documentation map
73
+ - [docs/architecture.md](./docs/architecture.md) for package boundaries
74
+ - [docs/safety.md](./docs/safety.md) for approval and replay expectations
75
+
76
+ ## License
77
+
78
+ Apache-2.0
@@ -0,0 +1,171 @@
1
+ type PhysicalRiskLevel = "safe" | "low" | "medium" | "high" | "dangerous";
2
+ type PhysicalSessionStatus = "idle" | "starting" | "ready" | "running" | "awaiting-input" | "complete" | "stopping" | "stopped" | "error";
3
+ type PhysicalExecutionMode = "simulation" | "hardware" | "hybrid" | "unknown";
4
+ type PhysicalObservationKind = "rgb" | "depth" | "point-cloud" | "joint-state" | "pose" | "text" | "video" | "artifact";
5
+ type PhysicalFrame = "world" | "robot-base" | "camera" | "tool" | string;
6
+ interface PhysicalVector3 {
7
+ x: number;
8
+ y: number;
9
+ z: number;
10
+ }
11
+ interface PhysicalQuaternionWxyz {
12
+ w: number;
13
+ x: number;
14
+ y: number;
15
+ z: number;
16
+ }
17
+ interface PhysicalPose {
18
+ position: PhysicalVector3;
19
+ orientation?: PhysicalQuaternionWxyz;
20
+ frame?: PhysicalFrame;
21
+ }
22
+ interface PhysicalImageObservation {
23
+ kind: "rgb" | "depth";
24
+ source: string;
25
+ width?: number;
26
+ height?: number;
27
+ mimeType?: string;
28
+ dataUrl?: string;
29
+ uri?: string;
30
+ frame?: PhysicalFrame;
31
+ timestamp?: number;
32
+ }
33
+ interface PhysicalTextObservation {
34
+ kind: "text";
35
+ source: string;
36
+ text: string;
37
+ timestamp?: number;
38
+ }
39
+ interface PhysicalStructuredObservation {
40
+ kind: Exclude<PhysicalObservationKind, "rgb" | "depth" | "text">;
41
+ source: string;
42
+ data: unknown;
43
+ frame?: PhysicalFrame;
44
+ timestamp?: number;
45
+ }
46
+ type PhysicalObservationItem = PhysicalImageObservation | PhysicalTextObservation | PhysicalStructuredObservation;
47
+ interface PhysicalObservation {
48
+ sessionId: string;
49
+ status?: PhysicalSessionStatus;
50
+ taskId?: string;
51
+ summary?: string;
52
+ items: PhysicalObservationItem[];
53
+ metadata?: Record<string, unknown>;
54
+ timestamp: number;
55
+ }
56
+ interface PhysicalTaskSpec {
57
+ id: string;
58
+ description: string;
59
+ goal?: string;
60
+ environment?: string;
61
+ mode?: PhysicalExecutionMode;
62
+ metadata?: Record<string, unknown>;
63
+ }
64
+ interface PhysicalSafetyPolicy {
65
+ riskLevel?: PhysicalRiskLevel;
66
+ requiresApproval?: boolean;
67
+ requiresHumanPresence?: boolean;
68
+ allowedModes?: PhysicalExecutionMode[];
69
+ emergencyStopRequired?: boolean;
70
+ notes?: string[];
71
+ }
72
+ interface PhysicalCapability {
73
+ name: string;
74
+ description: string;
75
+ safety?: PhysicalSafetyPolicy;
76
+ inputSchema?: unknown;
77
+ outputSchema?: unknown;
78
+ metadata?: Record<string, unknown>;
79
+ }
80
+ interface PhysicalExecutionRequest {
81
+ code: string;
82
+ language?: "python" | "typescript" | "javascript" | string;
83
+ timeoutMs?: number;
84
+ dryRun?: boolean;
85
+ metadata?: Record<string, unknown>;
86
+ }
87
+ interface PhysicalOutcome {
88
+ success: boolean;
89
+ reward?: number;
90
+ taskCompleted?: boolean;
91
+ terminated?: boolean;
92
+ truncated?: boolean;
93
+ reason?: string;
94
+ metadata?: Record<string, unknown>;
95
+ }
96
+ interface PhysicalArtifact {
97
+ id: string;
98
+ kind: "code" | "log" | "image" | "video" | "json" | "directory" | "other";
99
+ uri: string;
100
+ label?: string;
101
+ mimeType?: string;
102
+ metadata?: Record<string, unknown>;
103
+ }
104
+ interface PhysicalExecutionTrace {
105
+ id: string;
106
+ startedAt: number;
107
+ completedAt?: number;
108
+ request?: PhysicalExecutionRequest;
109
+ stdout?: string;
110
+ stderr?: string;
111
+ observations?: PhysicalObservation[];
112
+ artifacts?: PhysicalArtifact[];
113
+ outcome?: PhysicalOutcome;
114
+ metadata?: Record<string, unknown>;
115
+ }
116
+ interface PhysicalSessionState {
117
+ sessionId: string;
118
+ status: PhysicalSessionStatus;
119
+ task?: PhysicalTaskSpec;
120
+ mode?: PhysicalExecutionMode;
121
+ startedAt?: number;
122
+ updatedAt: number;
123
+ message?: string;
124
+ metadata?: Record<string, unknown>;
125
+ }
126
+ interface PhysicalSessionStartOptions {
127
+ task?: PhysicalTaskSpec;
128
+ metadata?: Record<string, unknown>;
129
+ }
130
+ interface PhysicalObserveOptions {
131
+ includeImages?: boolean;
132
+ includeArtifacts?: boolean;
133
+ maxItems?: number;
134
+ }
135
+ interface PhysicalListArtifactsOptions {
136
+ kind?: PhysicalArtifact["kind"];
137
+ limit?: number;
138
+ }
139
+ interface PhysicalSession {
140
+ readonly id: string;
141
+ readonly capabilities?: readonly PhysicalCapability[];
142
+ getState(): Promise<PhysicalSessionState> | PhysicalSessionState;
143
+ start?(options?: PhysicalSessionStartOptions): Promise<PhysicalSessionState>;
144
+ reset?(options?: PhysicalSessionStartOptions): Promise<PhysicalSessionState>;
145
+ observe?(options?: PhysicalObserveOptions): Promise<PhysicalObservation>;
146
+ executeCode?(request: PhysicalExecutionRequest): Promise<PhysicalExecutionTrace>;
147
+ listArtifacts?(options?: PhysicalListArtifactsOptions): Promise<PhysicalArtifact[]>;
148
+ stop(reason?: string): Promise<PhysicalSessionState>;
149
+ }
150
+ interface PhysicalAdapter<TOptions = unknown> {
151
+ readonly name: string;
152
+ createSession(options: TOptions): Promise<PhysicalSession> | PhysicalSession;
153
+ }
154
+ interface PhysicalToolMetadata {
155
+ physical?: {
156
+ sessionId: string;
157
+ status?: PhysicalSessionStatus;
158
+ observation?: PhysicalObservation;
159
+ trace?: PhysicalExecutionTrace;
160
+ artifacts?: PhysicalArtifact[];
161
+ state?: PhysicalSessionState;
162
+ };
163
+ [key: string]: unknown;
164
+ }
165
+
166
+ declare const defaultPhysicalSafetyPolicy: Required<Pick<PhysicalSafetyPolicy, "riskLevel" | "requiresApproval" | "requiresHumanPresence">>;
167
+ declare function normalizePhysicalSafetyPolicy(policy: PhysicalSafetyPolicy | undefined): PhysicalSafetyPolicy;
168
+ declare function isModeAllowed(mode: PhysicalExecutionMode | undefined, policy: PhysicalSafetyPolicy | undefined): boolean;
169
+ declare function describePhysicalState(state: PhysicalSessionState): string;
170
+
171
+ export { type PhysicalAdapter, type PhysicalArtifact, type PhysicalCapability, type PhysicalExecutionMode, type PhysicalExecutionRequest, type PhysicalExecutionTrace, type PhysicalFrame, type PhysicalImageObservation, type PhysicalListArtifactsOptions, type PhysicalObservation, type PhysicalObservationItem, type PhysicalObservationKind, type PhysicalObserveOptions, type PhysicalOutcome, type PhysicalPose, type PhysicalQuaternionWxyz, type PhysicalRiskLevel, type PhysicalSafetyPolicy, type PhysicalSession, type PhysicalSessionStartOptions, type PhysicalSessionState, type PhysicalSessionStatus, type PhysicalStructuredObservation, type PhysicalTaskSpec, type PhysicalTextObservation, type PhysicalToolMetadata, type PhysicalVector3, defaultPhysicalSafetyPolicy, describePhysicalState, isModeAllowed, normalizePhysicalSafetyPolicy };
package/dist/index.js ADDED
@@ -0,0 +1,41 @@
1
+ // src/safety.ts
2
+ var defaultPhysicalSafetyPolicy = {
3
+ riskLevel: "dangerous",
4
+ requiresApproval: true,
5
+ requiresHumanPresence: true
6
+ };
7
+ function normalizePhysicalSafetyPolicy(policy) {
8
+ return {
9
+ ...defaultPhysicalSafetyPolicy,
10
+ ...policy ?? {}
11
+ };
12
+ }
13
+ function isModeAllowed(mode, policy) {
14
+ if (!policy?.allowedModes || policy.allowedModes.length === 0) {
15
+ return true;
16
+ }
17
+ if (!mode) {
18
+ return false;
19
+ }
20
+ return policy.allowedModes.includes(mode);
21
+ }
22
+ function describePhysicalState(state) {
23
+ const parts = [`status=${state.status}`];
24
+ if (state.mode) {
25
+ parts.push(`mode=${state.mode}`);
26
+ }
27
+ if (state.task?.id) {
28
+ parts.push(`task=${state.task.id}`);
29
+ }
30
+ if (state.message) {
31
+ parts.push(`message=${state.message}`);
32
+ }
33
+ return parts.join(", ");
34
+ }
35
+ export {
36
+ defaultPhysicalSafetyPolicy,
37
+ describePhysicalState,
38
+ isModeAllowed,
39
+ normalizePhysicalSafetyPolicy
40
+ };
41
+ //# sourceMappingURL=index.js.map
@@ -0,0 +1 @@
1
+ {"version":3,"sources":["../src/safety.ts"],"sourcesContent":["import type {\n PhysicalExecutionMode,\n PhysicalSafetyPolicy,\n PhysicalSessionState,\n} from \"./types.js\";\n\nexport const defaultPhysicalSafetyPolicy: Required<\n Pick<\n PhysicalSafetyPolicy,\n \"riskLevel\" | \"requiresApproval\" | \"requiresHumanPresence\"\n >\n> = {\n riskLevel: \"dangerous\",\n requiresApproval: true,\n requiresHumanPresence: true,\n};\n\nexport function normalizePhysicalSafetyPolicy(\n policy: PhysicalSafetyPolicy | undefined,\n): PhysicalSafetyPolicy {\n return {\n ...defaultPhysicalSafetyPolicy,\n ...(policy ?? {}),\n };\n}\n\nexport function isModeAllowed(\n mode: PhysicalExecutionMode | undefined,\n policy: PhysicalSafetyPolicy | undefined,\n): boolean {\n if (!policy?.allowedModes || policy.allowedModes.length === 0) {\n return true;\n }\n if (!mode) {\n return false;\n }\n return policy.allowedModes.includes(mode);\n}\n\nexport function describePhysicalState(state: PhysicalSessionState): string {\n const parts = [`status=${state.status}`];\n if (state.mode) {\n parts.push(`mode=${state.mode}`);\n }\n if (state.task?.id) {\n parts.push(`task=${state.task.id}`);\n }\n if (state.message) {\n parts.push(`message=${state.message}`);\n }\n return parts.join(\", \");\n}\n"],"mappings":";AAMO,IAAM,8BAKT;AAAA,EACF,WAAW;AAAA,EACX,kBAAkB;AAAA,EAClB,uBAAuB;AACzB;AAEO,SAAS,8BACd,QACsB;AACtB,SAAO;AAAA,IACL,GAAG;AAAA,IACH,GAAI,UAAU,CAAC;AAAA,EACjB;AACF;AAEO,SAAS,cACd,MACA,QACS;AACT,MAAI,CAAC,QAAQ,gBAAgB,OAAO,aAAa,WAAW,GAAG;AAC7D,WAAO;AAAA,EACT;AACA,MAAI,CAAC,MAAM;AACT,WAAO;AAAA,EACT;AACA,SAAO,OAAO,aAAa,SAAS,IAAI;AAC1C;AAEO,SAAS,sBAAsB,OAAqC;AACzE,QAAM,QAAQ,CAAC,UAAU,MAAM,MAAM,EAAE;AACvC,MAAI,MAAM,MAAM;AACd,UAAM,KAAK,QAAQ,MAAM,IAAI,EAAE;AAAA,EACjC;AACA,MAAI,MAAM,MAAM,IAAI;AAClB,UAAM,KAAK,QAAQ,MAAM,KAAK,EAAE,EAAE;AAAA,EACpC;AACA,MAAI,MAAM,SAAS;AACjB,UAAM,KAAK,WAAW,MAAM,OAAO,EAAE;AAAA,EACvC;AACA,SAAO,MAAM,KAAK,IAAI;AACxB;","names":[]}
package/docs/README.md ADDED
@@ -0,0 +1,32 @@
1
+ # @cuylabs/physical-core Docs
2
+
3
+ `@cuylabs/physical-core` defines agent-agnostic physical AI contracts.
4
+
5
+ Use it for shared session, observation, artifact, capability, safety, trace, and
6
+ outcome types. It should not depend on an agent runtime or a concrete robotics
7
+ backend.
8
+
9
+ Start here:
10
+
11
+ - [Architecture](./architecture.md) explains the package boundary and why
12
+ robotics-specific semantics live outside the core contracts.
13
+ - [Safety](./safety.md) describes how physical capabilities should interact
14
+ with approvals, replay, and stop controls.
15
+
16
+ ## Core Concepts
17
+
18
+ `PhysicalSession` is the central contract. A session represents one simulator,
19
+ robot, or embodied runtime episode. It can expose status, observation,
20
+ artifacts, optional reset/start operations, optional code execution, and stop
21
+ control.
22
+
23
+ `PhysicalObservation` is a timestamped set of observation items. Items can be
24
+ images, depth, point clouds, joint state, poses, text summaries, video
25
+ references, or artifacts.
26
+
27
+ `PhysicalCapability` is descriptive metadata for what a backend can do. It
28
+ exists separately from model-facing tools because physical capabilities need
29
+ safety policy, world-state assumptions, and backend metadata.
30
+
31
+ `PhysicalExecutionTrace` captures what happened after a policy or command was
32
+ executed: stdout, stderr, observations, artifacts, and outcome.
@@ -0,0 +1,74 @@
1
+ # Physical Core Architecture
2
+
3
+ `@cuylabs/physical-core` keeps physical-world concepts independent from any one
4
+ agent runtime while still making them available to applications that need to
5
+ coordinate embodied systems.
6
+
7
+ ```text
8
+ Application or agent harness
9
+ -> PhysicalSession
10
+ -> backend adapter
11
+ -> simulator, robot, sensors, task state, and artifacts
12
+ ```
13
+
14
+ The shared contract should stay small. It is allowed to know about physical
15
+ sessions, observations, capabilities, traces, outcomes, artifacts, and safety
16
+ policy. It should not know how to launch CaP-X, connect to ROS 2, authenticate
17
+ to a simulator, manage robot hardware, or send joint commands.
18
+
19
+ The agent or workflow loop stays above this package. A host decides when to
20
+ observe, how to reason over observations, whether to generate policy code,
21
+ whether to ask for approval, and whether to continue or stop. This package only
22
+ defines the shared physical vocabulary those loops can use.
23
+
24
+ ## What Belongs Here
25
+
26
+ - Backend-neutral session and observation types
27
+ - Capability and safety metadata
28
+ - Execution trace, outcome, and artifact records
29
+ - Replay and stop-control semantics for physical side effects
30
+
31
+ ## What Belongs In Binding Packages
32
+
33
+ - Model-facing tools for a specific agent runtime
34
+ - Approval integration for a specific host framework
35
+ - Prompt or instruction packages for a specific model loop
36
+ - Agent construction helpers
37
+
38
+ For `@cuylabs/agent-core`, those pieces live in
39
+ `@cuylabs/physical-agent-core`.
40
+
41
+ ## What Belongs In Backend Packages
42
+
43
+ - Process launch and lifecycle for a specific runtime
44
+ - Transport protocols and service clients
45
+ - Backend-specific artifact discovery
46
+ - Simulator or robot-specific observation mapping
47
+ - Backend-specific helper APIs, such as turn history, skill libraries, or
48
+ rendered frames
49
+ - Any command vocabulary that only makes sense for one backend
50
+
51
+ For CaP-X, those pieces live in `@cuylabs/physical-capx`.
52
+
53
+ ## CaP-X Mapping
54
+
55
+ CaP-X maps naturally as a backend adapter because it is already a Python
56
+ robotics framework for Code-as-Policies robot manipulation:
57
+
58
+ ```text
59
+ CaP-X YAML config -> PhysicalTaskSpec
60
+ CaP-X env/trial -> PhysicalSession
61
+ CaP-X render/logs -> PhysicalObservation
62
+ CaP-X outputs folder -> PhysicalArtifact[]
63
+ CaP-X reward/completed -> PhysicalOutcome
64
+ ```
65
+
66
+ The adapter should not duplicate CaP-X internals. It should launch, connect to,
67
+ or call CaP-X and translate the results into these contracts. For live
68
+ agent-owned CaP-X loops, the adapter talks to a runtime bridge such as
69
+ `capx-agent-runtime`; `@cuylabs/physical-core` itself still only defines the
70
+ generic session and safety contract.
71
+
72
+ That split enables bring-your-own-agent. Any agent or workflow host can use the
73
+ same physical contracts, CaP-X can remain the Python robotics runtime, and
74
+ agent-specific packages can add their own tool and approval surfaces.
package/docs/safety.md ADDED
@@ -0,0 +1,37 @@
1
+ # Physical Safety
2
+
3
+ Physical contracts are conservative by default.
4
+
5
+ Direct execution of policy code should be treated as:
6
+
7
+ - `riskLevel: "dangerous"`
8
+ - non-parallel
9
+ - manually replayed
10
+ - side-effecting outside the language runtime
11
+ - approval-gated when hardware or irreversible simulator state is involved
12
+
13
+ That default is intentional. Replaying a tool call that moved a simulator or
14
+ robot can change state again, and replaying against hardware can be unsafe.
15
+
16
+ ## Approval Expectations
17
+
18
+ Applications should require explicit approval for hardware sessions and for any
19
+ capability that can cause motion, contact, heating, cutting, navigation, or
20
+ other physical side effects.
21
+
22
+ Simulation-only sessions can loosen the policy, but they should still treat
23
+ state-mutating execution as non-parallel and non-replayable unless the backend
24
+ provides snapshots and deterministic restore.
25
+
26
+ ## Stop Control
27
+
28
+ Every concrete `PhysicalSession` must implement `stop(reason)`. The exact
29
+ guarantee depends on the backend, but the method is the common control-plane
30
+ surface for UIs, middleware, runtime interruption, and emergency-stop flows.
31
+
32
+ ## Metadata
33
+
34
+ Safety policy in `@cuylabs/physical-core` is descriptive. It does not enforce
35
+ approval by itself. Binding packages and host applications are responsible for
36
+ turning `PhysicalSafetyPolicy` metadata into approval prompts, dispatch policy,
37
+ logs, and runtime controls.
package/package.json ADDED
@@ -0,0 +1,53 @@
1
+ {
2
+ "name": "@cuylabs/physical-core",
3
+ "version": "0.1.1",
4
+ "description": "Agent-agnostic physical AI contracts for sessions, observations, capabilities, safety, and traces",
5
+ "type": "module",
6
+ "main": "./dist/index.js",
7
+ "types": "./dist/index.d.ts",
8
+ "exports": {
9
+ ".": {
10
+ "types": "./dist/index.d.ts",
11
+ "import": "./dist/index.js",
12
+ "default": "./dist/index.js"
13
+ }
14
+ },
15
+ "files": [
16
+ "dist",
17
+ "docs",
18
+ "README.md"
19
+ ],
20
+ "devDependencies": {
21
+ "@types/node": "^22.0.0",
22
+ "tsup": "^8.0.0",
23
+ "typescript": "^5.7.0",
24
+ "vitest": "^4.0.18"
25
+ },
26
+ "keywords": [
27
+ "physical-ai",
28
+ "robotics",
29
+ "embodied-ai",
30
+ "safety"
31
+ ],
32
+ "author": "cuylabs",
33
+ "license": "Apache-2.0",
34
+ "repository": {
35
+ "type": "git",
36
+ "url": "https://github.com/cuylabs-ai/physical-ai-ts.git",
37
+ "directory": "packages/physical-core"
38
+ },
39
+ "engines": {
40
+ "node": ">=20"
41
+ },
42
+ "publishConfig": {
43
+ "access": "public"
44
+ },
45
+ "scripts": {
46
+ "build": "tsup --config tsup.config.ts",
47
+ "dev": "tsup --config tsup.config.ts --watch",
48
+ "typecheck": "tsc --noEmit",
49
+ "test": "vitest run",
50
+ "test:watch": "vitest",
51
+ "clean": "rm -rf dist"
52
+ }
53
+ }