ChiefOS — network operations that train while you troubleshoot
ChiefOS turns troubleshooting and validation into a self-documenting training record, at the edge, on accreditable models. The chat is the interface; the record is the product.
An edge-deployable platform organized around TOPL — Training exercises (NTC, JRTC, VALEX, CPX), daily Operations, mission Planning, and on-node Learning (Team Chief Academy, Network+). Same Chief, same knowledge base across modes. Works disconnected. Your unit's procedures. Human warrant retains authority.
The problem
- One comms cell supporting 20+ dispersed elements can't be everywhere at once
- Operator proficiency varies widely across dispersed nodes
- Communicators get pulled forward for tasks that should not require them
- Network bring-up and outage reporting slow the mission
- Unit knowledge is lost every rotation
What leadership gets
- OperationsFaster network validation across the formation
- Operations · PlanningMore nodes validated without pulling senior comms forward
- TrainingDocumented outages and after-action records — automatically
- TrainingConsistent operator performance across all elements
- Training → LearningInstitutional knowledge that survives PCS
Not a chatbot. A workflow participant.
The ticket-to-AAR flow below is how ChiefOS participates inside Operations — with a human-gated handoff into Training (exercise AAR) and Learning (knowledge base and academy). The macro-loop: plan the window → run the exercise or mission → capture lessons in the AAR → feed the knowledge base → drill the next rotation in Team Chief Academy on what the unit actually learned.
Ticket opens
Issue detected on mission; Chief auto-kicks off guidance bound to the ticket
Operator works it
Validation coach walks checklist; Chief cites unit knowledge base; operator executes
Chief confirms & resolves
Operator reports fix; Chief confirms and closes ticket; 5W outage report → PDF
AAR captures everything
Chat, checklist state, and resolution persist into the after-action record — during daily ops or a VALEX/JRTC/NTC window
Lessons promote to knowledge base
AAR findings enter a promotion queue — a human warrant approves what enters the knowledge base. The Chief only teaches in Learning what your 255N signed off on.
Hawkeye cascade — Chief correlates across the encryption boundary
SATCOM sync loss → BGP session drop → TACLANE peer unreachable → loud NIPR symptoms at the user desktop. An operator sees “network down.” Chief walks the cascade in order — underlay before overlay, encryption boundary before routing — citing your unit's kit and TTPs from the on-node knowledge base. One ticket, one thread, one AAR record when it closes.
Validate in Training. Learn on the node. Document in Operations — without exporting rows to an enterprise LMS.
Training · Operations · Planning · Learning
Four distinct pillars — not interchangeable labels. Training is NTC, JRTC, VALEX, CPX, and unit validation exercises. Learning is Team Chief Academy, Network+, and LMS-style skill work on the air-gapped node. Plan the window, run ops or the exercise, capture what happened, promote what warrants approve, drill the next rotation on what the unit actually learned.
Training
Field validation exercises — NTC, JRTC, VALEX, CPX, and unit CPXs where the formation proves readiness on the kit.
Operations
Ticket-bound troubleshooting, validation checklists, and shift handoff on the active mission.
Planning
Mission authoring, manifest, readiness gates, and validation catalog before the window opens.
Learning
Team Chief Academy, Network+, guided modules, fault drills, and LMS-style skill development — all on the air-gapped node.
Runs at the edge
Works disconnected on the node. No cloud, no reachback, no NIPR dependency. Survives EMCON and contested transport.
Your procedures
On-node knowledge base holds YOUR unit's kit, transports, TTPs, and SOPs. Doctrine corrections go in the knowledge base, not generic model defaults.
Human in charge
Chief coaches and documents. Operators execute. Warrants retain authority. Chief confirms the operator's reported fix — soldiers still verify.
Three surfaces on one node — each tagged to the TOPL pillars it serves.
Ask Chief
Same Chief, same knowledge base — context-adaptive across every TOPL mode.
- Operations: live issue coach, ticket-bound guidance, validation checklists, 5W outage reports → PDF
- Training: coach during NTC, JRTC, VALEX, CPX, and unit validation exercise windows
- Learning: Team Chief Academy and Network+ instructor; doctrine-grounded retrieval and citation chips
- Planning: mission setup, readiness context, shift-handoff injection
- Lineage: Ask Chief iOS app — 3,000+ soldier adopters since March 2023
Team Chief Academy
The drill your team runs in the lab is built from the outage your unit worked last rotation.
- Learning surface on the node — not a field exercise; complements NTC/JRTC/VALEX, not a replacement
- Guided learning modules, fault drills, Network+ prep on the air-gapped node
- Live Lab Console: real CLI into lab topology
- Guided / Coach / Exam modes — warrant still certifies
- Team chief builds training roster; readiness rolls up to weakest member per skill area
- Configure new drills without redeploying the platform
Planning · Mission & AAR
- Mission authoring, manifest, shift schedules, operating windows, lab topology
- Readiness gate before activation — manifest, personnel, validation catalog checked before the window opens
- Training exercise windows — VALEX, CPX, and unit validation schedules alongside daily ops
- Active issue tracking with diagnostic steps
- AAR moderation and closeout with persisted issue log
Enterprise LMS mindset
- Per-soldier transcript warehouses disconnected from the node
- Courses assigned in isolation; no team rollup
- Validation checklists live in a different system
- Readiness is a spreadsheet, not an exercise outcome
ChiefOS learning stack
- Mix guided modules, drills, and Network+ on one node
- Team chief assembles a training team from the roster
- Team skill level = weakest member in each area
- Mission validation proves the formation, not a database row
“Train the team on the kit. The record stays on the kit.”
100% air-gapped
Fully air-gapped deployment — no external connectivity required, ever. Accreditable model stacks per mission partner requirements. No Chinese-origin model dependency.
Accredited COTS baseline
Deploys on commercial off-the-shelf hardware and software stacks the mission partner accredits.
Secure SDLC
Security+ credentialed delivery; RMF/ATO artifacts by prime. TK self-performs ChiefOS integration, FSR support, and operator/maintainer training.
From Ask Chief to ChiefOS
In 2023, while still on active duty, the principal shipped Ask Chief — an iOS conversational AI advisor with 3,000+ soldier adopters in the earliest months of public LLMs — and ComStat, a battalion-level NetOps platform adopted voluntarily by Signal soldiers. ChiefOS is the edge platform evolution: same mission fluency, now on the kit, with training, validation, and AAR built in.
Start with a pilot
Deploy on 4–5 highest-pain nodes. Prove faster bring-up, more consistent operator performance, and better records — then scale across the formation. Pilot packages available under simplified acquisition thresholds through TK Tech Venture as prime (SDVOSB).
Pricing provided on request. Capability discussions welcome at TechNet Augusta and partner evaluations.
ChiefOS is a product of TK Tech Venture, LLC. ChiefOS software, screenshots, workflows, and related materials are protected by U.S. copyright law; copyright registration filed.
Unauthorized copying, redistribution, scraping, or reverse engineering of ChiefOS interfaces, workflows, or depicted functionality is prohibited except under written authorization from TK Tech Venture, LLC.
© 2026 TK Tech Venture, LLC. All rights reserved.
Unclassified · For official use only where applicable · Proprietary
The Chief replaces absence — not the warrant.