AIM Getting Started — Part 4: Trust, teamwork & ownership cost

[00:00] Part 4: Trust, teamwork & ownership cost
Part four closes the Getting Started series. Parts one through three walked decide, deliver, sustain, and observe. Now we open the doors those chapters teased: how teams collaborate inside AIM, how every scored recommendation stays cryptographically auditable, and how lifecycle affordability is defended before capital is committed.

[00:11] Work Queue — what is waiting on me
Start with the Work Queue. This is where roles become real — technical-to-acquisition handoffs, independent document review, Pulse blockers, Sustainment change requests, and governance decisions waiting on you. Not another inbox. A governed list of what this organization still owes the decision trail.

[00:32] Team, roles & security log
Open Team Management. Invite with an explicit role — Owner, Admin, Engineer, Analyst, Reviewer, or Viewer — so capability matches responsibility. Members, pending invitations, and approval authorities stay visible. Owners and Admins can open the Security Log — platform actions that matter for audit without dumping production secrets onto a demo tape.

[00:51] Document review queue
The Document Review Queue is the handoff surface between generation and sign-off. Filter pending, approved, or flagged work. Approving or flagging creates the human checkpoint that procurement and leadership expect — independent of whoever clicked Generate.

[01:07] Guest collaborators
Back on the assessment, open Review — guest collaborators. Invite an architect, contracting partner, or agency SME by email. Choose Viewer, Commenter, or Contributor and scope the sections they can touch. They get a one-time link — no AIM seat consumed — and every access event is logged.

[01:24] Help & documentation
When operators get stuck, they do not leave AIM for a PDF binder. Open Help and documentation — the Operator Guide walks assessment through sustainment, roles at a glance, and where to ask Eagle inside the workspace.

[01:39] Ask Eagle
Open AIM Eagle. Ask a grounded question about this organization’s work. Eagle answers with org context when retrieval allows — then stop and read the finished answer. Eagle is bounded help. It does not replace RAO scoring, cost models, or the audit trail.

[02:02] Why this rank
Return to Recommendations. Rank is not a mystery shortlist. Each pick shows RAO score, tier, and dimension fit so leadership can see why a path leads — and what trade-offs remain — before commitment.

[02:22] Decision provenance
Under Reports, open Decision Provenance Records. AIM stores cryptographic integrity for decision outputs so a recommendation can be traced after the fact — not just trusted because someone remembered the meeting. Export when an auditor or Board asks for the trail.

[02:44] Lifecycle affordability + Layer 1
Open the TCO Calculator. Set the projection period, include physical infrastructure when Layer one is in scope, and calculate. Wait for Total TCO and Monthly Average — then expand the breakdown. This is how leadership defends Year two, three, and five ownership cost before capital is committed — not after the invoice arrives.

[03:13] Data, privacy & accessibility
Finally, the public trust surfaces: Data and Privacy, and Accessibility. Retention windows, how AI is handled, and who AIM is built to serve. Getting Started Parts one through four are the operator path. Learn More stays the encyclopedia when you need depth.

[03:30] Series complete
That completes the Getting Started series. Intake and decision outputs. Delivery and sustainment. Observation without mutation. Collaboration, provenance, and lifecycle affordability on one continuous trail a CIO, Board, or auditor can defend.

End of Part 4.