Arkive/arkive
1
0
Fork 0
Code Issues 18 Pull requests 1 Projects Releases Packages Wiki Activity Actions

[Duplicate] Prevent local-content contamination and validate the complete overlay flow #42

New issue
Closed
opened 2026-07-31 01:21:16 -04:00 by JackFrostbyte · 1 comment
JackFrostbyte commented 2026-07-31 01:21:16 -04:00
Owner
Copy link

Goal

Prove end to end that user-side acquisition expands a local installation without
contaminating Arkive's redistributable bundle, release process, or diagnostics.

Required scenarios

  1. Validate a reviewed fixture recipe.
  2. Acquire from a local test server or manually import a fixture.
  3. Produce local-only documents and chunks.
  4. Build the separate local index.
  5. Search core and local indexes together.
  6. Resolve exact citations from both domains.
  7. Build the portable core bundle and prove no local byte, record, checksum, index,
    log, or path is included.
  8. Withdraw/expire the fixture recipe and verify future acquisition fails closed
    while existing local provenance remains honest.
  9. Run the flow under the constrained-resource profile from Issue #28.

Release guardrails

  • Explicit allowlist of core release inputs.
  • Hard failure on local-overlay paths or local-only records.
  • Source-control ignores for default local paths.
  • Secret scanning and log redaction checks.
  • Support/diagnostic bundles exclude local source text and sensitive provenance by
    default.
  • User documentation warns that backups or exports containing the overlay may not
    be redistributable.

Deliverables

  • End-to-end test suite.
  • Release contamination tests.
  • Portable deployment documentation.
  • User-facing legal/distribution notices and backup/export warnings.
  • Maintainer runbook for recipe withdrawal and incident response.

Acceptance criteria

  • The complete local workflow passes without internet access.
  • The core bundle is byte-for-byte unaffected by presence of local content.
  • Release jobs fail when deliberately presented with local-only inputs.
  • No credential or sensitive local provenance appears in logs or diagnostics.
  • Constrained-resource execution remains within documented limits.
  • User notices are shown at acquisition and export/backup boundaries.

Out of scope

  • Publishing a production recipe catalogue.
  • Legal approval of individual third-party targets.
## Goal Prove end to end that user-side acquisition expands a local installation without contaminating Arkive's redistributable bundle, release process, or diagnostics. ## Required scenarios 1. Validate a reviewed fixture recipe. 2. Acquire from a local test server or manually import a fixture. 3. Produce local-only documents and chunks. 4. Build the separate local index. 5. Search core and local indexes together. 6. Resolve exact citations from both domains. 7. Build the portable core bundle and prove no local byte, record, checksum, index, log, or path is included. 8. Withdraw/expire the fixture recipe and verify future acquisition fails closed while existing local provenance remains honest. 9. Run the flow under the constrained-resource profile from Issue #28. ## Release guardrails - Explicit allowlist of core release inputs. - Hard failure on local-overlay paths or local-only records. - Source-control ignores for default local paths. - Secret scanning and log redaction checks. - Support/diagnostic bundles exclude local source text and sensitive provenance by default. - User documentation warns that backups or exports containing the overlay may not be redistributable. ## Deliverables - End-to-end test suite. - Release contamination tests. - Portable deployment documentation. - User-facing legal/distribution notices and backup/export warnings. - Maintainer runbook for recipe withdrawal and incident response. ## Acceptance criteria - [ ] The complete local workflow passes without internet access. - [ ] The core bundle is byte-for-byte unaffected by presence of local content. - [ ] Release jobs fail when deliberately presented with local-only inputs. - [ ] No credential or sensitive local provenance appears in logs or diagnostics. - [ ] Constrained-resource execution remains within documented limits. - [ ] User notices are shown at acquisition and export/backup boundaries. ## Out of scope - Publishing a production recipe catalogue. - Legal approval of individual third-party targets.
JackFrostbyte commented 2026-07-31 01:35:56 -04:00
Author
Owner
Copy link

Closing this issue as a duplicate of #50.

Issues #42 and #50 were created with the same roadmap
content during recovery from an interrupted automation run. The later set
#43–#50 is canonical because Issue #34's finalized roadmap body, roadmap comment,
and dependency graph reference that set.

No implementation work was completed in this duplicate issue.

<!-- arkive-roadmap-duplicate-cleanup-v1 --> Closing this issue as a duplicate of #50. Issues #42 and #50 were created with the same roadmap content during recovery from an interrupted automation run. The later set #43–#50 is canonical because Issue #34's finalized roadmap body, roadmap comment, and dependency graph reference that set. No implementation work was completed in this duplicate issue.
JackFrostbyte changed title from Prevent local-content contamination and validate the complete overlay flow to [Duplicate] Prevent local-content contamination and validate the complete overlay flow 2026-07-31 01:35:57 -04:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feature/issue-17-reproducibility-tests
develop
No results found.
Labels
Clear labels
  
area/deployment
Portable packaging and constrained-environment validation

  
area/governance
Project rules, policies, contributor workflow

  
area/metadata
Schemas, manifests, validation contracts

  
area/pipeline
Import, extraction, normalization, chunking

  
area/search
Indexing, retrieval, citation resolution

  
type/data
Source selection, metadata, fixtures, and corpus work

  
type/design
Architecture, policy, contracts, and ADR work

  
type/implementation
Production code or tooling

  
type/testing
Reproducibility, integration, evaluation, and benchmark work

No labels
area/deployment
area/governance
area/metadata
area/pipeline
area/search
type/data
type/design
type/implementation
type/testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
Arkive/arkive#42
No description provided.