Background
CoreLink is one product across multiple implementation repositories. This work is owned by cli under EPIC-05.
Problem
The repository does not yet provide a supported, reproducible and acceptance-tested way to deliver secure authentication, tenant context, device, command, and diagnostics workflows.
Goal
Deliver secure authentication, tenant context, device, command, and diagnostics workflows, aligned with tagged contracts and the shared CoreLink release train.
Parent
- Primary Product Epic: EPIC-05
- Backlog ID:
CLI-02
Scope
- Deliver the title outcome inside
cli.
- Reconcile contract version, authentication, tenancy, error, compatibility, packaging and documentation behavior where applicable.
- Retain evidence for the Beta gate.
Out of Scope
- Hand-written divergence from the normative contracts.
- Unsupported production claims before an artifact and conformance evidence exist.
- A separate repository roadmap.
Acceptance Criteria
Technical Notes
Generated artifacts must identify immutable contract provenance. Security-sensitive tools use least privilege, explicit consent, audit and safe token handling. Package channels must distinguish prerelease from stable.
Dependencies
- Blocked by: CLI-01, supported APIs
- Blocks: Resolved during refinement.
- Cross-repository: Link concrete contract, mock, documentation and release Issues.
Planning Metadata
- Type: Feature
- Priority: P1
- Product milestone: Beta
- Domains: devex, api
- Area: package
- Complexity: L
- Initial status: Triage
- DRI: Unassigned
- Intended labels:
type:feature, priority:p1, domain:devex, domain:api, area:package
Definition of Done
Background
CoreLink is one product across multiple implementation repositories. This work is owned by
cliunder EPIC-05.Problem
The repository does not yet provide a supported, reproducible and acceptance-tested way to deliver secure authentication, tenant context, device, command, and diagnostics workflows.
Goal
Deliver secure authentication, tenant context, device, command, and diagnostics workflows, aligned with tagged contracts and the shared CoreLink release train.
Parent
CLI-02Scope
cli.Out of Scope
Acceptance Criteria
Technical Notes
Generated artifacts must identify immutable contract provenance. Security-sensitive tools use least privilege, explicit consent, audit and safe token handling. Package channels must distinguish prerelease from stable.
Dependencies
Planning Metadata
type:feature,priority:p1,domain:devex,domain:api,area:packageDefinition of Done