OSS-first docs
These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.
Export the evidence set attached to an execution-lane run.
Goal
Make evidence handoff explicit and auditable for operators.
Context
Used when exporting lane evidence for review, replay, or packaging.
Source Definition
import { ScalarTypeEnum, SchemaModel } from '@lssm-tech/lib.schema';
import { defineCommand } from '../../operations';
import {
CONTROL_PLANE_DOMAIN,
CONTROL_PLANE_OWNERS,
CONTROL_PLANE_STABILITY,
CONTROL_PLANE_TAGS,
} from '../constants';
export const ControlPlaneExecutionEvidenceExportCommand = defineCommand({
meta: {
key: 'controlPlane.execution.evidence.export',
title: 'Export Execution Lane Evidence',
version: '1.0.0',
description: 'Export the evidence set attached to an execution-lane run.',
goal: 'Make evidence handoff explicit and auditable for operators.',
context:
'Used when exporting lane evidence for review, replay, or packaging.',
domain: CONTROL_PLANE_DOMAIN,
owners: CONTROL_PLANE_OWNERS,
tags: [...CONTROL_PLANE_TAGS, 'execution', 'evidence'],
stability: CONTROL_PLANE_STABILITY,
},
capability: {
key: 'control-plane.audit',
version: '1.0.0',
},
io: {
input: ControlPlaneExecutionEvidenceExportInput,
output: ControlPlaneExecutionEvidenceExportOutput,
},
policy: {
auth: 'admin',
pii: [],
},
});