tegwick
a83ef0a79a
Classify freedom-intelligence for State Hub (agents domain), sync FI-WP-0001..0003 with hub IDs, enrich catalog entries with profile/SWOT, and pin the open-weight reserve to D:\vault\coulomb\freedom-intelligence\ with strategic S-tier policy.
125 lines
5.4 KiB
Markdown
125 lines
5.4 KiB
Markdown
# INTENT
|
||
|
||
> This file captures **why this repository exists**,
|
||
> the **direction it is moving toward**, and
|
||
> the **kind of system it is meant to become**.
|
||
> It is intentionally **aspirational and stable**, not a description of current implementation.
|
||
>
|
||
> Founding record: `history/InitialExploration.md`
|
||
|
||
---
|
||
|
||
## One-liner
|
||
|
||
**The just-in-case open-weights model lab** — Coulomb/NetKingdom sensing and reserve for AI capability, cost, and operable local intelligence.
|
||
|
||
---
|
||
|
||
## Why This Exists
|
||
|
||
AI capability is moving faster than any single product roadmap. Frontier models, open weights, training recipes, and agent harnesses shift monthly. Most organizations either:
|
||
|
||
* chase every vendor announcement without durable memory, or
|
||
* lock into a single cloud API and lose optionality when prices, licenses, or access change.
|
||
|
||
Coulomb NetKingdom needs a third posture:
|
||
|
||
1. **Sense** what actually moves capability, cost, accessibility, and operability.
|
||
2. **Reserve** open-weight artifacts that may matter later for local training or operations.
|
||
3. **Bias** toward intelligence that can be inspected, specialized, and run under our control.
|
||
|
||
Freedom Intelligence is that lab — not a chat product, not a public model CDN, and not a commitment to *run* every frontier model on today’s GPUs.
|
||
|
||
The open-weight **reserve** (VAULT bulk store under `D:\vault\coulomb\`) deliberately includes the **most
|
||
capable open models** we are allowed to retain, even when they are larger than
|
||
current lab inference can serve. Runnability and reservability are separate
|
||
axes: we sense the frontier, keep optionality offline, and grow runtime later.
|
||
|
||
---
|
||
|
||
## Mission
|
||
|
||
> *Where we are going.*
|
||
|
||
Become the Coulomb NetKingdom **intelligence sensing loop and open-weight strategic reserve**:
|
||
|
||
* a **daily research brief** that filters noise into lab-relevant signal across four standing axes;
|
||
* a **deliberate collection** of open-weight models (and justified companions) on backup-class storage;
|
||
* durable in-repo memory (briefs, inventory metadata, research notes) that outlives any single session or vendor.
|
||
|
||
---
|
||
|
||
## Standing axes (the permanent lens)
|
||
|
||
| Axis | Focus |
|
||
| ---- | ----- |
|
||
| **A — Frontier** | Best-of-class capabilities, benchmarks, and price-point trends |
|
||
| **B — Edge / local / open** | Low-cost open and local compute intelligence and specializations |
|
||
| **C — Homelab training** | Pre-, mid-, post-, and domain specialization recipes that fit lab hardware |
|
||
| **D — Harness & fleet** | Agent harnesses, orchestration, sandboxing, and fleet management |
|
||
|
||
These axes define *what we watch*, not a promise to implement every technology we report on.
|
||
|
||
---
|
||
|
||
## Dual loops
|
||
|
||
```text
|
||
Daily research brief ──► Sensing loop (awareness, prioritization)
|
||
Open-weight reserve ──► Strategic reserve (optionality for train / run)
|
||
```
|
||
|
||
The brief feeds collection candidates. Collection never mirrors the entire Hub — only high-leverage, clearly licensed, hard-to-reobtain artifacts.
|
||
|
||
---
|
||
|
||
## Design principles
|
||
|
||
* **Signal over noise** — report what changes capability, cost, access, or operability.
|
||
* **Just in case** — hold optionality without obligation to *serve* every model today.
|
||
* **Capability-first reserve** — prefer the strongest open weights (license-clean), not only what fits current VRAM.
|
||
* **Catalog in git, blobs on bulk store** — metadata is versioned; weights live on `D:\vault\coulomb\freedom-intelligence\`.
|
||
* **License and integrity first** — no collection that terms forbid; checksums and provenance required.
|
||
* **Homelab honesty** — prefer methods and models that fit our real hardware envelope.
|
||
* **Operable intelligence** — models without harness, sandbox, and fleet thinking are incomplete for NetKingdom.
|
||
* **Inspectable and open-leaning** — bias toward stacks we can audit and specialize.
|
||
|
||
---
|
||
|
||
## Strategic role in Coulomb / NetKingdom
|
||
|
||
| Freedom Intelligence supplies | Adjacent systems own |
|
||
| ----------------------------- | -------------------- |
|
||
| Field sensing and briefs | State Hub distribution / inbox (optional consumers) |
|
||
| Open-weight reserve + inventory | Backup facilities, storage ops, disaster-control policy |
|
||
| Guidance on what can run locally | sand-boxer, agent harnesses, local runtimes, llm-connect |
|
||
| Domain-specialization *candidates* | Domain repos that consume specialized models later |
|
||
|
||
It does **not** replace NetKingdom security, identity, ops, or application products.
|
||
|
||
---
|
||
|
||
## Intended users
|
||
|
||
* Operators and agents maintaining Coulomb/NetKingdom infrastructure who need a trusted daily AI field picture
|
||
* People deciding when to use frontier APIs vs local open weights
|
||
* Future local training / inference facilities that need a curated reserve and inventory
|
||
|
||
---
|
||
|
||
## Maturity target
|
||
|
||
A mature Freedom Intelligence lab should:
|
||
|
||
* produce a reliable **daily brief** with stable structure and cited sources;
|
||
* maintain a **living inventory** of reserved model revisions with integrity metadata;
|
||
* enforce a **collection policy** (approval thresholds, license gate, capacity budget);
|
||
* know its **hardware envelope** for “homelab accessible”;
|
||
* optionally distribute briefs into operator workflows (inbox / State Hub) without becoming a general news product;
|
||
* feed domain specialization work without owning every consumer pipeline.
|
||
|
||
---
|
||
|
||
## Stability note
|
||
|
||
Changes to this file represent a **deliberate shift** in why the lab exists or what dual loops it owns. Such changes should be rare. Near-term deliverables and boundaries live in `SCOPE.md`.
|