Cross-Cutting

The Ground

The enablers of movement.

The cross-cutting domains are not ground. They are reconnaissance, mobility and command — the things that make maneuver on ground possible. A force with no reconnaissance holds terrain blindly, a force with no mobility holds only what it is standing on, and a force with no command authority cannot commit to anything. None of the three is a position that can be taken, which is why they are modeled as enablers spanning the stack rather than as a tenth layer beneath it.

The modeling consequence is specific: these three are deliberately not gap-scored the same way. A coverage percentage on Identity means a proportion of identity terrain is defended. A coverage percentage on Visibility would mean nothing of the kind — visibility is not defended, it is possessed or not possessed, per layer. So the enablers are assessed on maturity and their effect is expressed as a constraint on the other nine rather than as a number added to them.

That constraint is real and it is the reason this section exists at all. Automation maturity sets the upper bound on how fast any maneuver can be executed; visibility maturity sets the upper bound on which maneuvers can be selected, because a form of maneuver you cannot observe the effect of cannot be validated; governance maturity sets what may be done without escalation. An estate with excellent tower coverage and Traditional enablers has ground it cannot maneuver on.

Key Terrain

Key terrain is what confers decisive advantage if you hold it. Everything else on this layer is defended in order to hold these.

• The telemetry pipelineThe reconnaissance asset. Its coverage decides which parts of the estate the defense can see contact on at all.
• The orchestration layerThe mobility asset. It converts a decision into an action at machine speed, or fails to, which is the difference between a scheme and a document.
• The rules of engagementCommand authority in written form. Nothing in the catalog can be executed under contact faster than the ROE permits.
• The cycle recordThe evidentiary product. It is what makes the framework auditable rather than merely operated.

The Decisive Point

Which defensive fires are pre-authorized without escalation

The decisive point is which defensive fires are pre-authorized without escalation.

This is a governance artifact, not a technical one, and it is decisive because it sets the ceiling on the entire framework’s central claim. Every form of maneuver in the catalog has an execution time, and for the contested ones — isolation, credential revocation, segment severing — that time is dominated by the authorization step rather than by the action. An agency whose containment requires a bridge call has an adversary tempo advantage that no additional tooling removes.

It is also the cheapest decisive point in the model to seize. Writing down which actions may be taken, under which conditions, by which role, without escalation, costs an afternoon of the Authorizing Official’s time and converts several maneuvers from theoretical to available. Very little else in this framework has that ratio.

Sub-Towers, Rung by Rung

Maturity is scored here, not on the layer. Each rung below is stated for this sub-tower specifically — “Advanced” means something testable on each one, and something different on each one. The rung marked current is the illustrative position on the Federal Reference Agency profile.

Weight, Coverage and Residual Risk

Weight is criticality × exposure, 1–25 per sub-tower. Coverage is the weighted mean of the sub-towers’ maturity coverage — never a flat average. Residual risk is reported both as the inverse percentage and in weight points, because the points are what rank a backlog.

• 37Layer weightSum of criticality × exposure across 3 sub-towers
• 56.8%Rolled-up coverageWeighted mean of the sub-tower maturity coverage
• 43.2%Residual riskThe inverse of coverage, before weight is considered
• 16Residual pointsWeight left uncovered — the figure that ranks against other layers

The enablers are not weighted with the towers, and the model would be wrong if they were. Adding a Visibility coverage percentage to nine terrain coverage percentages produces a tenth number that does not mean the same thing as the other nine and quietly dilutes them.

The enablers instead act as a stated constraint on the rollup. A mission consumer’s Bill of Defense carries its towers’ weighted coverage and, separately, the enabler maturity that bounds it — because a mission with 80 per cent tower coverage and Traditional automation cannot execute the maneuvers that coverage assumes.

The practical rule for an adopter: read the enablers first, then the towers. If automation is Traditional, most of the ranked backlog the towers produce is not executable this cycle, and the correct first move is on this layer rather than on the layer the backlog names.

Maneuvers That Consume This Layer

The primary list is derived from each form’s own primary-terrain declaration in the maneuver catalog, so the two cannot disagree. The supporting list is authored: “consumes without being principally about” is a judgment, and deriving it would be a false claim of rigour.

Controls That Apply

Two lists. The first is specific to this ground; the second is the spine every layer runs through, stated once here rather than repeated ten times across the reference.

Specific to TX

• CE-1 Cycle CadenceCycle cadence is the clock all three enablers are measured against.
• CE-2 Priority Intelligence RequirementsPriority intelligence requirements are what turn collection from a license question into a tasking question.
• CE-3 Fusion and ConfidenceFusion and confidence is the analytic half of the visibility enabler — telemetry with no confidence statement is data, not intelligence.
• CE-6 Cycle Record and TrendThe cycle record and trend is the evidentiary product the governance enabler exists to produce.
• CE-7 Brief Generation and DistributionBrief generation and distribution is how the running estimate reaches the authority that can act on it.
• CG-1 Defensive IntentDefensive intent — the single artifact from which every scheme of maneuver is derived.
• CG-2 Phase DeclarationPhase declaration, which changes what the rules of engagement permit without renegotiating them under contact.
• CG-3 Rules of EngagementRules of engagement: the decisive point on this layer, stated as a control.
• CG-4 Findings DispositionFindings disposition, which is what stops governance maturity from being a documentation exercise.
• TA-1 Decision Loop MeasurementDecision loop measurement is the mobility enabler’s primary metric.
• TA-3 Temporal Advantage ThresholdThe temporal advantage threshold states what the loop has to beat, without which the measurement has no verdict.
• TA-4 Pre-authorized ResponsePre-authorized response is where the ceiling on every contested maneuver is actually set.
• SM-1 Maneuver Catalog AdoptionManeuver catalog adoption is a governance act before it is an operational one.
• RC-5 Reconstitution ExerciseThe reconstitution exercise is the rehearsal that converts an automation claim into a demonstrated one.

The Common Spine

• TM-1 Terrain Inventory and OverlayPuts the layer’s elements on the overlay in the first place. Nothing below can be computed for terrain that is not inventoried.
• TM-2 Defensive Layer ClassificationAssigns each element to a layer. This is the control that decides whether a thing is scored here or somewhere else.
• TM-3 Asset WeightingSets criticality and exposure per asset, which is the allocation driver every coverage and residual-risk number on the layer is weighted by.
• TM-6 Terrain CurrencyAges the overlay. A layer’s coverage figure inherits the staleness of the inventory it was computed from.
• TM-7 Terrain OwnershipNames an owner for the ground, so a coverage gap has somebody to be assigned to.
• KT-1 Decisive Point IdentificationIdentifies the decisive point on this layer rather than accepting the one this page names by default.
• KT-2 Decisive Point Protection FloorSets the minimum protection the layer’s decisive point must hold regardless of its rolled-up coverage.
• FO-7 Obligation Profile DeclarationDeclares which federal obligations bind the estate, which is what makes any FO coverage figure on this layer comparable to another agency’s.
• EN-1 Event Declaration and TriageAn engagement on this layer starts by being declared. Until it is, nothing below this line is running.
• EN-2 Engagement ReconstructionReconstruction is what establishes how far the adversary actually got across this layer, and it is what corrects the dwell estimate the layer’s tempo figures use.
• EN-3 Evidence PreservationSets how long this layer’s telemetry must survive — measured against estimated dwell, not against a retention default.
• EN-4 Escalation and Engagement AuthorityNames who may authorize action on this layer out of hours, which is where the decide segment is usually spent.
• EN-5 Eradication and Transition to RecoveryVerifies the adversary is off this layer before the mission is restored onto it.
• EN-6 Engagement CommunicationReports what happened on this layer to those who must know, inside and outside the agency.
• SM-7 Deception EmplacementDeception is emplaced per layer, on the approaches to that layer’s decisive point — the one detection here with no false-positive budget.
• CE-4 Coverage and Residual Risk ComputationPerforms the coverage and residual-risk computation described below, on the cycle cadence.
• CE-5 Remediation Backlog PrioritizationTurns weight multiplied by coverage gap into a ranked backlog, which is what the layer’s numbers are for.