docs: specify local outcome export boundaries (#58) #96

Merged
kilo merged 1 commit from issue-58-export-rights-spec into develop 2026-10-18 19:46:11 +00:00
Member

Scope

This is the expressly permitted local export/version/rights specification slice for #58. It distinguishes the current task schema-1 JSON, synthetic reference_export, and the pure core.outcomes.export_outcomes model, including what each source establishes and where usage, review/remediation, identity provenance, correlation, redaction, and current remote state remain absent or unknown.

The planned boundary preserves local-by-default operation, producer/schema identity, provenance, correction and Attempt lineage, unknowns, and the distinction between historical PR receipts and current remote state. It records that local JSON is not a redaction or sharing grant; Router #177 is a separate local consumer, and MI #17 rejects current operational intake. No new format/schema version, redactor, upload, service, MI receiver, calibration or user-data path is implemented. Whole-task cost collection and route/call identity still depend on #56/#52. Issue #58 remains open and this PR does not claim full acceptance.

Validation

  • make check: 1457 passed, 85 skipped, 106 subtests; Ruff, basedpyright, import boundaries, secret scan and diff checks passed.
  • make package-check: reproducible wheel/sdist, isolated install, and CLI/intake/source smoke checks passed.

Refs

Refs #58

Base: f7db85188a0c20438f2b3e8ccbbeb28ada012425
Head: 20e7f3e50361d80115f3a892566103ac59bf1973

No export was uploaded; no Router or MI behavior was invoked.

## Scope This is the expressly permitted local export/version/rights specification slice for #58. It distinguishes the current task schema-1 JSON, synthetic `reference_export`, and the pure `core.outcomes.export_outcomes` model, including what each source establishes and where usage, review/remediation, identity provenance, correlation, redaction, and current remote state remain absent or unknown. The planned boundary preserves local-by-default operation, producer/schema identity, provenance, correction and Attempt lineage, unknowns, and the distinction between historical PR receipts and current remote state. It records that local JSON is not a redaction or sharing grant; Router #177 is a separate local consumer, and MI #17 rejects current operational intake. No new format/schema version, redactor, upload, service, MI receiver, calibration or user-data path is implemented. Whole-task cost collection and route/call identity still depend on #56/#52. Issue #58 remains open and this PR does not claim full acceptance. ## Validation - `make check`: 1457 passed, 85 skipped, 106 subtests; Ruff, basedpyright, import boundaries, secret scan and diff checks passed. - `make package-check`: reproducible wheel/sdist, isolated install, and CLI/intake/source smoke checks passed. ## Refs Refs #58 Base: `f7db85188a0c20438f2b3e8ccbbeb28ada012425` Head: `20e7f3e50361d80115f3a892566103ac59bf1973` No export was uploaded; no Router or MI behavior was invoked.
docs: specify local outcome export boundaries (#58)
All checks were successful
ci / check (pull_request) Successful in 2m28s
20e7f3e503
kilo merged commit 98656f6e6e into develop 2026-10-18 19:46:11 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Creatidy/creatidy-kernel!96
No description provided.