Landing

AI co-pilot for engineering leadership.

Unprecedented operational tempo of data-driven decision making with Human-AI Command Composite

Sign In Learn more

The daily command loop · Acts 5–12

From signal to accountable action.

Gjallarhorn assembles the situation. You bring judgment. Huginn preserves the evidence, executes the chosen outcome, and carries the learning into the next loop.

05 · Orient

Read the situation, not another dashboard.

Each sync becomes a frozen SitRep: assessed period, Rules of Engagement, Variables, applied FRAGOs, and the Decisions that now deserve command attention.

SitRep · Evidence · Proposed Decisions
HUGINNatlas-backend / SitRepRED
Situation Report · 28 Sep 14:30

Milestone risk requires a decision

Today 09:00 → 14:30 · RoE v4 · Auto trigger

Semi-Auto
Throughput18increments
Cycle Time8.4dtarget ≤ 5d
Quality82%coverage
Rework11%stable
1 · Situation AssessmentCritical

Release 1.21 is at risk. Three critical bugs remain open and median cycle time has crossed the command threshold.

  • Cycle Time8.4d actual · ≤ 5d expected
  • Milestone3 critical bugs · due Monday
  • ContextFriday bug belay applied
06 · Calibrate

Change the doctrine without erasing the record.

A FRAGO explains a legitimate exception in flight. Scope it, time-box it, and verify exactly which SitReps used it.

Project-scoped · Versioned · Auditable
HUGINNFRAGOs / atlas-backendActive
Rules of Engagement adjustment

Friday bug belay

Affects Active Bug Count (ABC) · Project atlas-backend

Enabled
BodyMarkdown
Friday release tolerance

Belay the zero-bug expectation on Fridays. Up to 3 active bugs is acceptable while release verification is underway.

Effective windowFridays · through 31 Oct
07 · Explain

See when the signal changed—and why.

Every Variable trajectory is reconstructed from immutable SitRep datapoints. Select any point to inspect its period, source plan, and original assessment.

Variable trajectory · Provenance · Drill-down
HUGINNatlas-backend / VariablesToday
Rules of Engagement · v4

Cycle Time (CT)

Median time from first increment to completed work

Last 8 hours ▾
Variable trajectory8.4 days
09:0010:3012:0013:1514:30
≤ 5d 5–7d > 7d
08 · Interrogate

Ask the question the report did not answer.

Gjallarhorn reasons inside the selected Project, grounds its answer in live evidence, and keeps tool work inspectable instead of hiding it behind a confident paragraph.

Grounded in SitRep · Project memory · Tool trace
HUGINNGjallarhorn / atlas-backendGrounded
ContextSitRep #142RoE v42 active FRAGOs
Why did Cycle Time turn red today if throughput stayed green?
Gjallarhorn

Throughput is healthy because 18 increments landed, but 11 belong to work already in progress. Three long-running critical bugs crossed the seven-day threshold, lifting median Cycle Time to 8.4 days.

SitRep #142CT datapoint23 UoWs
Tool trace · 3 callsget_sitrep(142) → get_variable("CT") → list_uows(age_days ≥ 7)
Ask Gjallarhorn…
09 · Decide

Choose the outcome—and leave the reasoning behind.

Approve one bounded calibration or dispatch, reject with optional vigilance, or write your own. The action and your rationale become durable command memory.

Outcome options · Human judgment · Decisions Logic
HUGINNDecision / D-442Proposed
Source SitRep #142 · High confidence

Stabilize the release path before Monday

Owner: Commander · Mode: Semi-Auto

2 breaches
Gjallarhorn's case7 evidence items

Cycle time is rising because critical bugs are aging, not because delivery stopped. Protect the milestone by dispatching targeted stabilization work.

CalibrationMonitor through a FRAGORetune the threshold for this release window.
Recommended · DispatchCreate Jira stabilization issueAssign the three critical bugs as one bounded task.Selected
CustomType your ownRoute another bounded outcome.
10 · Verify reality

Inspect contribution without collapsing people into a score.

Follow the underlying increments and work items day by day. Identity reconciliation keeps source handles together while the evidence remains available for review.

Activity timeline · Reconciled identity · Source records
HUGINNContributors / Anton P.This week
Reconciled contributor

Anton Petrov

anton@company.com · @antonp · Jira anton.petrov

Mapped
Activity timeline23 increments · 8 UoWs
Mon8 / 3
Tue5 / 2
Wed6 / 1
Thu4 / 2
Fri0 / 0
feat9f8a2c1Release health endpoint
fixHUG-291Close retry loop regression
11 · Confirm dispatch

Know that the work landed where execution happens.

Action Stations is a read-only Jira mirror for successful dispatches. Huginn shows current state and provenance; the team keeps working in its system of record.

Read-only Jira mirror · Dispatch provenance · Sync
HUGINNAction StationsSynced
Read-only Jira mirror

4 active dispatches

Last sync 14:38 · HUGINN-labelled issues

↻ Sync
Project: AllStatus: Open + In progressAssignee: All
KeySummaryStatusAssigneeProjectUpdated
HUGINN-302 ↗Stabilize release 1.21 critical pathIn progressAnton P.Atlas2m ago
HUGINN-298 ↗Restore canary coverage gateOpenMaria S.Atlas1h ago
HUGINN-287 ↗Document rollback ownershipDonePriya N.PlatformYesterday
Jira remains the system of record. No edits are made from this screen.
12 · Compound

Carry today’s context into every future loop.

Situational Awareness is workspace-wide narrative memory: durable constraints, active situations, source Decisions, and a version trail that explains what changed.

Workspace-wide narrative memory · Versions · Decision links
HUGINNSituational Awarenessv12 · Current
Workspace-wide narrative memory

Context every SitRep should know

Shared across all Projects · Read-only view

Edit
Standing context2 entries
Core team owns ingestion
Donland · 10 Apr

Platform Engineering is accountable for ingestion reliability and connector policy.

Release authority
Priya N. · 18 Apr

Production promotion remains an explicit Commander decision.

Active situationsThis week
GitLab rate-limit window
Source Decision D-438 · 28 Sep

Expect delayed sync completion during the migration window; do not interpret gaps as team inactivity.