Documentation#
Install and operate a local console for Linux clusters. FICC connects to approved SSH profiles and keeps inventory, operation history and message records on the controller. Start with the guides below, then use the task manuals as needed.
The online documentation provides page contents, command copying and a search index that runs in your browser.
Start here#
- Read the architecture and security model.
- Choose a Linux package or source installation.
- Try the demonstration console with separate state.
- Connect a machine and inspect its pinned identity.
- Set up normal startup and maintenance.
Manual library#
| Order | Manual | Subject |
|---|---|---|
| 01 | Architecture | Controller, node helpers, trust and state ownership. |
| 02 | Installation | Requirements, build, demo and first machine enrollment. |
| 03 | Operation | Desktop startup, service settings, trust changes and upgrades. |
| 04 | Managed jobs | Command previews, resource controls, output and recovery. |
| 05 | Files | Registered roots, explorer tables, file changes and transfers. |
| 06 | Terminals | Interactive SSH, tmux, tiling, fullscreen and session lifetime. |
| 07 | Coding agents | Runtime profiles, native adapters, inbox tools and authority. |
| 08 | Agent bus | Run membership, explicit delivery, receipts and portable history. |
| 09 | Backup and restore | Consistent private state bundles and verified restore. |
| 10 | History archives | Explicit retention, export and capacity recovery. |
| 11 | Local API | Authentication, scopes, endpoints and request contracts. |
| 12 | Testing | Source, Python, SSH, browser and installed-system checks. |
| 13 | Dependencies | Locked components, bundled assets and their licences. |
| 14 | Linux packages | Binary formats, verification, first startup, upgrade and removal. |
Terms used in the manuals#
| Term | Meaning |
|---|---|
| Controller | The local FICC service and its canonical database. |
| Node | An enrolled machine reached through a pinned SSH identity. |
| SSH profile | A locally approved SSH alias used for connection and enrollment. |
| Agent profile | An exact installed command, adapter and working directory on one node. |
| File root | A registered directory with explicit permitted actions. |
| Run | A host-owned group of enrolled agents and their bus messages. |
| Receipt | Evidence of a delivery stage, separate from task completion. |
| Reconcile | Inspect a saved operation identity after its outcome became uncertain. |
| Archive | Explicitly preserve completed history before reclaiming active capacity. |
Find a task#
| Task | Start here |
|---|---|
| Install a binary package | Linux packages |
| Try FICC without touching nodes | Demo mode |
| Start from the application menu | User service |
| Open several terminals | Terminal workspace |
| Register a coding agent | Coding agents |
| Contact another agent | Agent bus |
| Prepare a controller upgrade | Operation and backup |
| Reclaim retained capacity | History archives and closed bus runs |
Conventions#
Commands use generic machine aliases and opaque IDs. Replace those values with the identities shown by the local console. Keep credentials in protected files; never put them in command arguments, repository text or shared captures.
Each guide states its own prerequisites, effects and limits. A preview does not perform an operation. A receipt does not prove completed work. Active and uncertain records remain retained until their outcome can be resolved.