Create a portable non-AI proof-loop bundle #27

New issue

Open

opened 2026-07-24 19:38:23 -04:00 by JackFrostbyte · 0 comments

JackFrostbyte commented

2026-07-24 19:38:23 -04:00

Owner

Goal

    Create a developer-grade portable artifact containing the approved archive subset, metadata, processed records, lexical index, manifest, search runtime, and offline run instructions.

    ## Why

    The proof loop must be transferable to another Linux environment to demonstrate that Arkive is not dependent on the development checkout, homelab, internet, or AI services.

    ## Scope

    - Define a narrowly scoped developer proof-bundle layout.

Include only approved source material and its required attribution or license information.
Include validated source, document, and chunk records.
Include the lexical index and validated index manifest.
Include the search and citation-resolution runtime.
Include required local dependencies or precise offline installation instructions.
Add a deterministic or clearly documented bundle-build command.
Record bundle contents and integrity information appropriate to this developer artifact.

Test transfer and execution in another Linux environment.

  ## Out of scope

  - A production public release format.

Automatic updates, signing infrastructure, installers, bootable images, or platform-specific packages.
Model files, embeddings, LLMs, translation, or speech.

The entire future Arkive corpus.

  ## Dependencies

  - #26 — Add the complete AI-independent offline proof-loop test

  ## Acceptance criteria

  - The bundle contains every component required for the non-AI proof loop and no unapproved source.

A second Linux environment can install or run it without network access.
Search results resolve to exact included source passages.
The index manifest and artifact integrity checks pass after transfer.
The artifact does not depend on the homelab or development checkout.

Build and usage instructions are documented.

  ## Validation

  - Build the bundle from a clean checkout.

Transfer it to a clean VM or container that does not mount the repository.
Disable networking and run representative searches and citation resolution.
Verify bundle contents and integrity.

Confirm no AI or embedding component is present.

  ## Suggested branch

  `feature/issue-27-portable-proof-bundle`

  <!-- arkive-planning-automation:2026-07-24-v3:M2-09 -->

## Goal Create a developer-grade portable artifact containing the approved archive subset, metadata, processed records, lexical index, manifest, search runtime, and offline run instructions. ## Why The proof loop must be transferable to another Linux environment to demonstrate that Arkive is not dependent on the development checkout, homelab, internet, or AI services. ## Scope - Define a narrowly scoped developer proof-bundle layout. - Include only approved source material and its required attribution or license information. - Include validated source, document, and chunk records. - Include the lexical index and validated index manifest. - Include the search and citation-resolution runtime. - Include required local dependencies or precise offline installation instructions. - Add a deterministic or clearly documented bundle-build command. - Record bundle contents and integrity information appropriate to this developer artifact. - Test transfer and execution in another Linux environment. ## Out of scope - A production public release format. - Automatic updates, signing infrastructure, installers, bootable images, or platform-specific packages. - Model files, embeddings, LLMs, translation, or speech. - The entire future Arkive corpus. ## Dependencies - #26 — Add the complete AI-independent offline proof-loop test ## Acceptance criteria - The bundle contains every component required for the non-AI proof loop and no unapproved source. - A second Linux environment can install or run it without network access. - Search results resolve to exact included source passages. - The index manifest and artifact integrity checks pass after transfer. - The artifact does not depend on the homelab or development checkout. - Build and usage instructions are documented. ## Validation - Build the bundle from a clean checkout. - Transfer it to a clean VM or container that does not mount the repository. - Disable networking and run representative searches and citation resolution. - Verify bundle contents and integrity. - Confirm no AI or embedding component is present. ## Suggested branch `feature/issue-27-portable-proof-bundle`

JackFrostbyte added this to the Offline Search Proof Loop v0.1 milestone

2026-07-24 19:38:23 -04:00

JackFrostbyte added the

area/deployment

type/implementation

labels

2026-07-24 19:38:23 -04:00

JackFrostbyte added a new dependency

2026-07-24 20:10:51 -04:00

#26 Add the complete AI-independent offline proof-loop test

JackFrostbyte added a new dependency

2026-07-24 20:10:51 -04:00