Air-gap strategy
Define what remains local, what is separated, and which environments require no outside network dependency.
Model hosting tiers
Match the system to the use case, team size, workflow weight, and supportable hardware footprint.
Internal document ingestion
Map policies, SOPs, documentation, and internal references into a retrieval system that stays under customer control.
Backups, logs, and maintenance
Build the support and oversight structure at the same time as the deployment, not afterward.
Air-gapped architecture
Clarify what internal boundary design really means and when it matters most.
Local model hosting
Explain how owned hardware and model operations become a maintained business capability.
Knowledge ingestion
Explain how internal documents, permissions, and retrieval quality shape the usefulness of the system.
Security and governance
Give the infrastructure story a stronger enterprise edge with access control and change discipline.
| Infrastructure concern | Astrum role | GCT role |
|---|---|---|
| System architecture | Define deployment logic, software layer, and access model | Deliver and stage the physical platform |
| Power and placement | Define operational requirements | Coordinate site readiness and hardware install |
| Internal portal access | Define user experience and knowledge behavior | Ensure the environment is installed and reachable on site |
| Support path | Own software maintenance and operational model | Support physical equipment and field needs |