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

Create Arkive project foundation documentation #2

New issue
Closed
opened 2026-06-03 19:14:17 -04:00 by JackFrostbyte · 1 comment
JackFrostbyte commented 2026-06-03 19:14:17 -04:00
Owner
Copy link

Summary

Create the first real foundation documentation for the Arkive project.

Arkive is intended to become a curated, legally redistributable, multilingual, offline-first knowledge archive for survival, disaster recovery, and long-term civilization rebuilding.

This issue establishes the project identity, contribution workflow, early architecture direction, initial roadmap, monorepo-first decision, and first-draft policies for source acceptance, licensing, and AI answer behavior.

Scope

Create or update the following files:

  • README.md
  • CONTRIBUTING.md
  • CHANGELOG.md
  • governance/decision_records/ADR-0001-use-monorepo-first.md
  • docs/architecture/overview.md
  • docs/roadmap/initial-roadmap.md
  • meta/policies/source_acceptance_policy.md
  • meta/policies/license_policy.md
  • meta/policies/ai_answer_policy.md

Requirements

The foundation documentation should explain:

  • what Arkive is;
  • what Arkive is not;
  • the long-term goal of the project;
  • the offline-first philosophy;
  • the legal redistribution requirement;
  • the future AI/RAG direction;
  • the monorepo-first structure;
  • the current early status of the project;
  • the branch and PR workflow;
  • source acceptance expectations;
  • license handling expectations;
  • no-source-no-answer AI behavior;
  • source documents as the authority.

Out of scope

This issue does not include:

  • production code;
  • ingestion pipelines;
  • metadata schemas;
  • document collections;
  • generated indexes;
  • model files;
  • deployment bundles;
  • AGENTS.md.

AGENTS.md should be handled separately in Issue #2 so LLM-agent rules can be reviewed independently.

Acceptance criteria

  • The project purpose is clear.
  • The monorepo-first decision is documented.
  • Contributors understand the branch and PR workflow.
  • Source, license, and AI answer policies exist at a first-draft level.
  • The documentation does not overpromise implemented functionality.
  • The documentation clearly distinguishes current state from long-term goals.
  • The documentation preserves the principle that source documents are authoritative and AI is only an assisted interface.
  • AGENTS.md is not added in this issue.
## Summary Create the first real foundation documentation for the Arkive project. Arkive is intended to become a curated, legally redistributable, multilingual, offline-first knowledge archive for survival, disaster recovery, and long-term civilization rebuilding. This issue establishes the project identity, contribution workflow, early architecture direction, initial roadmap, monorepo-first decision, and first-draft policies for source acceptance, licensing, and AI answer behavior. ## Scope Create or update the following files: * `README.md` * `CONTRIBUTING.md` * `CHANGELOG.md` * `governance/decision_records/ADR-0001-use-monorepo-first.md` * `docs/architecture/overview.md` * `docs/roadmap/initial-roadmap.md` * `meta/policies/source_acceptance_policy.md` * `meta/policies/license_policy.md` * `meta/policies/ai_answer_policy.md` ## Requirements The foundation documentation should explain: * what Arkive is; * what Arkive is not; * the long-term goal of the project; * the offline-first philosophy; * the legal redistribution requirement; * the future AI/RAG direction; * the monorepo-first structure; * the current early status of the project; * the branch and PR workflow; * source acceptance expectations; * license handling expectations; * no-source-no-answer AI behavior; * source documents as the authority. ## Out of scope This issue does not include: * production code; * ingestion pipelines; * metadata schemas; * document collections; * generated indexes; * model files; * deployment bundles; * `AGENTS.md`. `AGENTS.md` should be handled separately in Issue #2 so LLM-agent rules can be reviewed independently. ## Acceptance criteria * The project purpose is clear. * The monorepo-first decision is documented. * Contributors understand the branch and PR workflow. * Source, license, and AI answer policies exist at a first-draft level. * The documentation does not overpromise implemented functionality. * The documentation clearly distinguishes current state from long-term goals. * The documentation preserves the principle that source documents are authoritative and AI is only an assisted interface. * `AGENTS.md` is not added in this issue.
JackFrostbyte commented 2026-06-03 19:14:32 -04:00
Author
Owner
Copy link

Completed

Issue #1 is complete.

This issue added the initial Arkive project foundation documentation and policy files.

Added or updated

  • README.md
  • CONTRIBUTING.md
  • CHANGELOG.md
  • governance/decision_records/ADR-0001-use-monorepo-first.md
  • docs/architecture/overview.md
  • docs/roadmap/initial-roadmap.md
  • meta/policies/source_acceptance_policy.md
  • meta/policies/license_policy.md
  • meta/policies/ai_answer_policy.md

Result

The project now has:

  • a clear description of what Arkive is and is not;
  • documented project principles;
  • an offline-first direction;
  • a legal redistribution requirement;
  • a source-authority and citation-backed AI direction;
  • a documented monorepo-first architectural decision;
  • an initial architecture overview;
  • an initial roadmap;
  • first-draft source acceptance, license, and AI answer policies;
  • a contribution workflow based on main, develop, and feature branches.

Validation

  • The combined diff was generated and reviewed through /tmp/arkive-issue-1-foundation.diff.
  • The documentation avoids claiming that runtime, ingestion, indexing, RAG, content packs, or deployment bundles already exist.
  • AGENTS.md was intentionally not added and remains reserved for a separate issue.

Closing as completed by the foundation documentation PR.

## Completed Issue #1 is complete. This issue added the initial Arkive project foundation documentation and policy files. ## Added or updated * `README.md` * `CONTRIBUTING.md` * `CHANGELOG.md` * `governance/decision_records/ADR-0001-use-monorepo-first.md` * `docs/architecture/overview.md` * `docs/roadmap/initial-roadmap.md` * `meta/policies/source_acceptance_policy.md` * `meta/policies/license_policy.md` * `meta/policies/ai_answer_policy.md` ## Result The project now has: * a clear description of what Arkive is and is not; * documented project principles; * an offline-first direction; * a legal redistribution requirement; * a source-authority and citation-backed AI direction; * a documented monorepo-first architectural decision; * an initial architecture overview; * an initial roadmap; * first-draft source acceptance, license, and AI answer policies; * a contribution workflow based on `main`, `develop`, and feature branches. ## Validation * The combined diff was generated and reviewed through `/tmp/arkive-issue-1-foundation.diff`. * The documentation avoids claiming that runtime, ingestion, indexing, RAG, content packs, or deployment bundles already exist. * `AGENTS.md` was intentionally not added and remains reserved for a separate issue. Closing as completed by the foundation documentation PR.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feature/issue-3-metadata-schemas-v0.1
develop
No results found.
Labels
Clear labels
No items
No labels
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#2
No description provided.