docs: specify local outcome export boundaries (#58) #96
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-58-export-rights-spec"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 purecore.outcomes.export_outcomesmodel, 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:
f7db85188a0c20438f2b3e8ccbbeb28ada012425Head:
20e7f3e50361d80115f3a892566103ac59bf1973No export was uploaded; no Router or MI behavior was invoked.