Historical IAS engineering archive
Frozen documentation from IAS's earlier engineering profile. It is preserved as evidence, not current product or setup guidance.
These documents preserve IAS's earlier repo-first engineering profile: a local runtime, reusable context, validators, approvals, evidence, and a thin control plane. They remain useful as historical implementation evidence, but they are frozen and do not define the current IAS product, supported setup path, availability, security commitment, or offer.
The current IAS direction starts with rough human intent and works toward useful outcomes through relevant context, visible assumptions, proportionate routing, autonomy within hard floors, and inspectable results. Return to the current IAS direction before drawing a product conclusion from this archive.
How to read the archive
- Commands such as
ias startrecord an earlier engineering workflow. They are not current setup instructions. - Hub, Console, Agent Framework, Context Lake, local-execution, approval, and security descriptions record the earlier profile. They require current revalidation before use as product or capability claims.
- Links below organize preserved evidence. A working page does not prove that its workflow is supported, available, or offered today.
Preserved engineering areas
| Area | Historical question it explored |
|---|---|
| Core concepts | How workspaces, goals, decisions, and run artifacts could relate |
| Architecture | How the repo-first framework and thin control plane were designed |
| Context Lake | How reusable project context could travel between runs |
| Execution modes | How different autonomy and review paths were modelled |
| Inbox | How structured human decisions could enter a run |
| Workboard | How the earlier Hub represented work and evidence |
For current product interpretation, use
docs/strategy/ias-north-star.md and apps/ias-landing/PRODUCT.md in the
Lucentive repository. This public archive is intentionally noindex and is not a
current onboarding journey.