You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ifrit, the offensive range's host, decided by ADR-0017 ("Buy ifrit for
IOPS and keep the range disposable") and specced there. #96 closed on the
decision and the runbook, and the purchase lost its tracker — the roadmap
still ends its entry with "what is left is the purchase itself and the
build", and ADR-0015 still says "ifrit is unpurchased". Same shape as #102 → #404 and #95 → #413; this is the tracker.
What is decided (ADR-0017)
Form: a quiet SFF or mini box, not rack-mounted, one NIC, on a Green
(VLAN 30) access port of neo and an outlet on the PDU.
Disk: NVMe. Not a spindle, not a mirror — the range is disposable by
decision and gets no backups and no PBS.
RAM: two socketed slots, 32 GB fitted; the second slot is the fix if
four concurrent targets and a BloodHound ingest do not fit — "a memory
kit rather than a machine".
Address: VLAN 30, per ADR-0014; the attack VM is its only dual-homed
guest, the targets sit on a bridge with no physical port.
What it waits on
ADR-0017 and build-the-playground.md §0 put three things ahead of it, and
they are now: #101's estate (the domain, #414, and the SOC stack, #266/#267)
— an attack VM pointed at an uninstrumented estate teaches nothing; #234's
tripwire (armed and verified 2026-09-08); #235 (decided, the iLO stays, and
the BMC hardened 2026-09-09). So the purchase is gated on #414 being built,
and is the last purchase on the estate's list, not the next.
build-the-playground.md §1–§9: rack, the two bridges, move Saruman
to 10.0.30.20, close the management plane, the attack VM, the targets,
the four properties, prove a leak reports itself.
The optional Loki rule from ADR-0014 (a 172.30.30.0/24 source logged
as a block on igc0.30) lands here, once the subnet is real.
Purchases this needs
The box. Nothing else — and a memory kit only if 32 GB proves short.
ifrit, the offensive range's host, decided by ADR-0017 ("Buy ifrit forIOPS and keep the range disposable") and specced there. #96 closed on the
decision and the runbook, and the purchase lost its tracker — the roadmap
still ends its entry with "what is left is the purchase itself and the
build", and ADR-0015 still says "
ifritis unpurchased". Same shape as#102 → #404 and #95 → #413; this is the tracker.
What is decided (ADR-0017)
(VLAN 30) access port of
neoand an outlet on the PDU.decision and gets no backups and no PBS.
four concurrent targets and a BloodHound ingest do not fit — "a memory
kit rather than a machine".
guest, the targets sit on a bridge with no physical port.
What it waits on
ADR-0017 and
build-the-playground.md§0 put three things ahead of it, andthey are now: #101's estate (the domain, #414, and the SOC stack, #266/#267)
— an attack VM pointed at an uninstrumented estate teaches nothing; #234's
tripwire (armed and verified 2026-09-08); #235 (decided, the iLO stays, and
the BMC hardened 2026-09-09). So the purchase is gated on #414 being built,
and is the last purchase on the estate's list, not the next.
Order of work
bought under Fit the two SSDs in Saruman, and re-derive what the spindles decided #418 are for
Saruman, not this box; Fit the two SSDs in Saruman, and re-derive what the spindles decided #418 says the rangestill needs NVMe of its own.
build-the-playground.md§1–§9: rack, the two bridges, moveSarumanto
10.0.30.20, close the management plane, the attack VM, the targets,the four properties, prove a leak reports itself.
172.30.30.0/24source loggedas a block on
igc0.30) lands here, once the subnet is real.Purchases this needs
The box. Nothing else — and a memory kit only if 32 GB proves short.