Internal tools come under Wallace IT umbrella - he owns the map, hosting, DR and access, builders keep maintaining, and unused tools get an evaluation date and are shut down

October 2, 2026 at 11:34 PMoperationalhigh

Situation

Every internal tool any part of CIQ sits on (Mother Brain, C3, Intelligence Hub, Outfitter, Gauntlet and others) moves under Steve Wallace as IT. Wallace owns visibility and overall management: a map of what exists, where it is hosted and who maintains it, plus uniform hosting, disaster recovery, backups and Okta access. Resources stay where they are - the original builder can keep maintaining Intelligence Hub from Wolford org, Ryan team can keep building. Start with Wallace maintaining a map. The SRE team carries the run-and-manage weight, partly as a dispassionate owner watching usage: each tool gets an evaluation date, and if nobody uses it (about three months) it is discussed at Peter staff meeting and shut down a month later if still unused.

Reasoning

Peter split Steve question into oversight versus labor, so Wallace gets accountability without needing headcount and without it reading as a land grab. Tools are CIQ assets, not their builders - the original builder moving off Ryan team showed how builder-owned tools get orphaned. Peter wants everyone free to build with AI, but once the company depends on something it needs consistent hosting, DR and access control that Ryan citizen-developer team cannot guarantee. The usage-based kill date is the core: a neutral owner watching traffic is how CIQ gets good at killing unused things and moving the dollars to higher-return places.

Additional Context

Raised by Steve Wallace on a dog walk; Peter offered to have mini-me draw up the proposal. Reiterated to Ryan the same afternoon and to Brian and Brady on 10/2.

Observed Evidence

Three meetings over two days, same structure stated each time: Wallace owns the map and the hosting/DR/access uniformity, builders keep maintaining, unused tools get shut down on an evaluation date.

Matching Patterns

60%
Demonstrate the Standard, Then Collect It(keyword match)
50%
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict(decides owner then gives usage criterion)

Confidence Breakdown

32/35
Evidence
12/30
Pattern
18/20
Source
14/15
Corroboration

Reasoning Depth Analysis

Org Signal:Internal tools are company assets with one place to ask about status, not the property of whoever built them
Who Affected:Ryan team, the original builder, Karl, Brady, Brian citizen-developer track, anyone depending on these tools
Precedent:Build freely, then a productize button moves it under the umbrella; survival is decided by usage
Consequences:Wallace starts with a map only; no labor transfer implied
Timing:the original builder moving teams, renewed C3 noise, and Steve raising it himself

Source

reflection

AI Confidence

76%

Related Context

🎥
Steve <> Peter Weekly 1:1

fathom

Intelligence Hub is CIQs, not Ryans... should live under IT, which in my mind lives under you... We start with you just maintaining a map.

🎥
Ryan <> Peter Weekly 1:1

fathom

I want that weight to fall on the SRE team. Partly, it is I want us getting good at killing things when they are not being used.

🎥
Brian / Brady Peter Weekly Sync

fathom

Anything that a portion of CIQ sits on top of... I want to be running in Wallaces world... if nobody uses it for three months, I want to shut it down.

Follow-up Todos

Suggest follow-up todo

Draft the internal-tools umbrella proposal for Wallace (map, hosting/DR/Okta, maintainers, evaluation dates)

@Steve

Mini-me mention from Peter Nelson via Steve 1:1 (Fathom 188825430), 2026-10-01

Why: Peter told Steve mini-me would draw up the proposal and send it over; Steve is waiting on it before moving anything, and without a written version the umbrella stays a conversation while tools like Intelligence Hub drift without an owner.

Outcome

No outcome recorded yet.

Decision ID: 16491045-bade-47ba-b66d-46111e78396c