freedom-intelligence/SCOPE.md
tegwick 46cfcd7a51 Align FI recurrence with activity-core + rein-aharness (drop workstation cron).
Document the three-layer model, add railiance-rhythm executor install, and
point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00

145 lines
5.7 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# SCOPE
> This file helps you quickly understand what this repository is about,
> when it is relevant, and when it is not.
> It is intentionally lightweight and may be incomplete.
>
> Aspirational charter: `INTENT.md` · Founding record: `history/InitialExploration.md`
---
## One-liner
Daily AI research briefs (models, methods, harness, tooling) plus an open-weight model reserve on lab backup storage — Coulomb/NetKingdom intelligence lab.
---
## Core Idea
Freedom Intelligence is a **sensing and reserve** repository:
1. Curated **daily research briefs** across axes AD (frontier, edge/local, training, harness/fleet).
2. **Inventory + collection policy** for open-weight models retained on backup-class storage for possible later local training or operations.
Git holds briefs, schemas, policies, and catalog metadata. Model weight blobs stay off hot cluster disks on designated backup storage.
---
## In Scope
### Research brief
- Daily brief production using `briefs/_template.md`
- Layout under `briefs/YYYY/MM/YYYY-MM-DD.md`
- Standing coverage of axes AD when there is signal
- Collection-candidate flagging for the model reserve
- Source citation and durable archive of briefs in-repo
### Model reserve
- Inventory schema and catalog entries (`inventory/`)
- Collection approval policy and license gate
- Backup storage target and capacity policy (`docs/backup-storage-policy.md`)
- Metadata required to rehydrate a revision (source, hash, license, size, hardware class)
- Companion artifacts when justified (tokenizers, adapters, small eval fixtures)
### Lab documentation
- INTENT / SCOPE / history
- Optional delivery notes for State Hub / operator inbox (`docs/state-hub-delivery.md`)
- Hardware envelope notes as they become known
---
## Out of Scope
| Concern | Belongs elsewhere |
| ------- | ----------------- |
| Public model mirror / CDN | Not this lab |
| 24/7 inference serving of the full reserve | Future ops facility / runtime repos |
| Frontier-scale pre-training from scratch | Hyperscale; not homelab commitment |
| Closed-weight collection or ToS-violating scrapes | Forbidden |
| Provider-neutral LLM client library | `llm-connect` |
| Console assistant UX | `can-you-assist` |
| Sandbox establishment service | `sand-boxer` |
| Platform identity / secrets / bootstrap | `net-kingdom`, `key-cape` |
| General disaster backup governance | `disaster-control` |
| Domain application fine-tune pipelines (end-to-end) | Domain repos; this lab only reserves bases and tracks methods |
---
## Relevant When
- You need the daily or historical AI field picture for Coulomb/NetKingdom decisions
- You are evaluating frontier vs open/local options (capability, price, license)
- You want to know whether an open-weight model is (or should be) in the lab reserve
- You are planning homelab-scale specialization and need method / model candidates
- You are designing agent harness or fleet work and want external signal on that axis
---
## Not Relevant When
- You need an LLM API client (use `llm-connect`)
- You need to provision agent sandboxes (use `sand-boxer`)
- You need platform IAM or secrets (use NetKingdom / KeyCape)
- You only need one-off news without archival brief or inventory discipline
---
## Current State
| Area | Status |
| ---- | ------ |
| Overall | **Operable lab** — foundation + **live** weekday brief schedule + R-spine reserve |
| INTENT / SCOPE | Drafted |
| Baseline survey | `research/2026-07-24-baseline-field-survey.md` |
| Briefs | 2026-07-24, 07-28, **08-03** (week catch-up); playbook + recurrence ops |
| Backup storage | **VAULT HD** `D:\vault\coulomb\freedom-intelligence\`; soft quota 850 GiB |
| Inventory | R verified; **Kimi K3** S1 approved+deferred (~1454 GiB); other S deferred; W candidate |
| Reserve policy | Capability-first — not gated by current VRAM |
| Activity-core | Definition **enabled on railiance**; Temporal schedule weekdays 07:30 Berlin |
| Executor | rein-aharness `fi-research-brief` via railiance user timer 07:35 (not workstation cron) |
| State Hub | Repo under **agents**; workplans finished + hub-indexed |
| Workplans | FI-WP-0001…0003 **finished** |
---
## How It Fits
| Direction | Systems |
| --------- | ------- |
| **Upstream** | Public model hubs, papers, pricing pages, release notes, harness projects |
| **Peer** | `llm-connect`, `sand-boxer`, `net-kingdom`, `disaster-control`, domain repos |
| **Downstream (future)** | Local inference/training facility, specialized domain agents, operator decision-making |
| **Distribution (optional)** | State Hub progress/inbox, operator mail/wiki |
---
## Near-term deliverables
1.`INTENT.md` / `SCOPE.md` / foundation docs
2. ✅ Brief template + playbook + sources allowlist
3. ✅ Baseline field survey + collection recommendations
4. ✅ Catalog candidates (P0/P1)
5. ✅ ActivityDefinition draft (disabled)
6. ⬜ Pin backup storage path and capacity budget (FI-WP-0001-T04)
7. ⬜ activity-core resolver + enable schedule (FI-WP-0002)
8. ⬜ Approve/download P0 reserve (FI-WP-0003)
9. ⬜ First daily delta brief (manual or after automation)
---
## Terminology
| Term | Meaning |
| ---- | ------- |
| **Brief** | Dated research digest under `briefs/` |
| **Axis AD** | Standing monitoring lenses (frontier, edge/local, training, harness) |
| **Reserve** | Open-weight collection on backup storage |
| **Catalog entry** | In-repo inventory metadata for one model revision |
| **Collection candidate** | Brief-flagged artifact not yet approved/collected |
| **Hardware envelope** | Lab hosts that define “homelab accessible” for B/C |
Preferred terms: research brief, open-weight reserve, inventory, collection policy.
Avoid: “mirror of Hugging Face”, “our AI product”, “always-on model zoo”.