Go2 Intelligence Package Internal discovery bundle · updated 2026-04-04
Package lanes

Start from a question

Use the menu only when you need the library. Most pages should explain themselves before you ever open this rail.

Start HereOrient quickly, get the shape of the company, and choose your path.
Mission ControlThe live front door: what matters now, where pressure is rising, and where to branch next.Choose Your PathIntent-based reading order for the whole package.Go2 In 15The quick company-level brief before you dive.Right NowThe sharpest current-state read on the business.Signal BoardThe highest-signal updates and open questions across the business right now.Revenue Growth PatternThe repeated sales/growth mechanics, the 2026 translation, and the faster route into the commercial story.How Go2 Actually RunsThe live operating manual, not the org-chart fiction.Operating System ExplorerInteractive view of routing, pressure, accounts, and tool-mediated reality.Pulse TimelineTwo-week focus, engagement, and strain shapes across company, divisions, departments, and key seats.2026 Year LensYear-to-date labor, visibility gaps, dark-after-carry seats, and the lanes the recent pulse is under-describing.Recent vs 2026Where the last-two-week pulse and the 2026 record disagree, what kind of disagreement it is, and which horizon should carry more weight.Focus AtlasCard-native view of what each lane-sized part of the company seems preoccupied with right now.Working Set LabUse pinned objects as working memory: compare them, trace paths between them, and keep their recent state in one place.CrossroadsThe stitched layer showing which objects really connect lanes and which ones should stay anchored.
Operator DeskPages for running the company, triaging risk, and deciding where human effort goes next.
Operator Desk OverviewThe operator-facing front door for priorities, failures, triggers, and control loops.Live Priority StackWhat deserves action now, in order.Intervention StackWhere intervention will buy back the most operating truth.Operating ScoreboardThe company-level outcome view without pretending the system is clean.Shadow Operating SystemThe invisible machinery actually keeping things moving.Failure ModesHow this system breaks and where it lies or goes dark.Fragile HandoffsThe relay chains most likely to fail or stall.Trigger LibrarySignals that should automatically provoke action.Judgment CallsThe recurring decisions that should not be improvised.Decision RightsWhere approvals and authority really live today.Exception BoardThe exception economy that is secretly running the company.Operator TriageWhat someone should do when they have to step in fast.Operator ScenariosLikely situations and how to respond without inventing from scratch.Run The WeekThe near-term operating cadence that matters.Operating RhythmRecurring forums, daily rooms, and the meeting-to-artifact echoes that show where cadence is real versus wasteful.Founder Control PlaneWhere founder attention is acting like infrastructure, plus the decision archaeology explaining why the lane looks this way.
Revenue and CashCommercial motion, expansion paths, and the money strain shaping every decision.
Revenue and Cash OverviewThe lane briefing for commercial reality, cash strain, and the rescueable middle of the book.Commercial CockpitThe commercial recovery lane, current motion, and where velocity is actually getting lost.Account PortfolioStrategic accounts, operator reality, and what is genuinely worth keeping in your head.Revenue Mechanics ExplorerThe repeated commercial mechanics across older growth surges and the live 2026 lane, shown as one inspectable surface.Historical Growth CyclesThe repeat sales-sprint pattern, revenue step-ups, and how the 2026 lane rhymes with the older cycles.Cash and TrustThe cash strain, payroll truth, and the trust damage it is causing.Live but Stalled LogosAccounts that still matter but are getting stuck in legal, routing, or execution drag.Opportunity MapExpansion wedges, sellable pain, and buried revenue surface area.Question AtlasThe unresolved commercial and operating questions still worth chasing.
People and WorkWho is actually doing the labor, how work is split, and where roles no longer fit reality.
People and Work OverviewThe lane briefing for labor, seat truth, hidden operators, and workstream reality.PeopleSeat-level pages, workload reads, and operator signals.DepartmentsDepartment-level operating reads and where capacity is really landing.DivisionsDivision-level patterns, drift, and labor concentration.FunctionsThe functional map of what the business is really doing.Owners and OperatorsWhere named ownership and actual operating behavior diverge.WorkstreamsThe actual lanes of work instead of task-label theater.JourneysObject-level journeys like selection, payroll, and launch loops.EntitiesNamed accounts, clients, and operational objects.Control SurfacesThe places where actual control or routing authority sits.Hidden Operator MapInvisible operators, proxy loops, and load-bearing seats.
Evidence and Deep DivesProof trails, story drilldowns, and the analysis surfaces that pressure-test the reads.
Evidence and Deep Dives OverviewThe lane briefing for claims, evidence, stories, and package pressure-testing.Truth MapThe high-level disagreement map between narrative and observed reality.Object RegistryCross-package registry of people, accounts, issues, stories, journeys, and claims.Artifact AtlasRecurring docs, rooms, queues, filtered views, and control surfaces promoted into named operating objects.CrossroadsWhere the package stops stacking pages and starts showing the few objects that genuinely connect lanes.Story MapThe operating stories that matter enough to trace.Story PagesThe full set of story drilldowns and linked reads.EvidenceWhere to inspect the proof surfaces directly.Operating NotebooksLong-form operating notes and stitched observations.Execution MapWhat people appear to be trying to accomplish and whether it looks like value or drift.Org DynamicsHow the company behaves as a social and operating system.Systems AtlasThe systems the company actually relies on and what they are being used for.Tool GraphTool-mediated behavior and where software is acting like labor.Narrative DriftWhere reports and management language diverge from observed work.Workload and RiskWho is carrying load, who is dark, and who looks strained or questionable.Who Talks To WhoThe communication and collaboration map that still reveals process truth.BlindspotsCoverage boundaries, misleading telemetry, stale seats, proxy operation, and which claims should be held lightly.Identity and Edge TrustWhich seats are proxy-operated, stale, or dark-but-still-real, and which communication edges deserve confidence versus suppression.What People Are Used ForRecipient-side communication truth: roles, request types, escalation loops, and direct versus adjacent evidence.Insight LabThe canonical person-insight layer that later rollups depend on.Assessment MatrixDimension-by-dimension call on the business instead of generic scores.Constraint MapThe bottlenecks that actually set the pace of the system.Belief LedgerWhere the company may be fooling itself or carrying untested assumptions.Capacity vs DemandWhere work demand is outrunning real human or system capacity.Solution BlueprintsThe strongest tool, automation, or AI-native wedges already visible.Claim RegisterWhat the package is asserting, why, and how confident it should be.Challenge LabWhere the package pressure-tests itself instead of pretending certainty.TopicsTopic clusters pulled out of the observed work itself.NeighborhoodsLocal operating neighborhoods in the org and communication graph.Frontier ReviewIndependent critiques and synthesis from frontier review runs.Process LearningsNotes on how this kind of package should be built better next time.
Recent pages
Founder Gravity
Mission Control/Operator Desk Overview/Founder Control Plane
Internal package · 2026-04-04

Scott Founder Control Plane

This page exists so the package can separate founder leverage from founder glue: which loops still route through the founder, which ones should be detached first, and what would actually stall if that bandwidth disappeared for a week.

Open nextOpen Operator Desk OverviewOpen Live Priority StackOpen Intervention Stack
ViewingFounder Control PlaneAction page Time horizonCurrent operations TrustCurated synthesis
Switch horizon
Pulse 2026 YTD Compare Last year
Click types Drillgo deeper Switchsame node, new lens Proofsupporting evidence

Where founder-bound control still appears

Scott is carrying the founder-led workflow-discovery / Cowork.ai book, and the current operating book already reads as 18 discos scheduled, 3 implementations, 4 negotiations, 2 implementation calls, 2 live, and 80 in pipe rather than vague top-of-funnel interest.
The company is also routing payroll, cash-trust narration, and partner exception pressure back into the same seat, which means founder bandwidth is being consumed by both revenue creation and credibility maintenance.
This is not just founder visibility or charisma. It is commercial conversion, product proof, bridge-money triage, and company-state explanation collapsing into one operator.
The workflow-discovery lane is not just a few warm emails. It is an assembled commercial system built from mined demos and discoveries, a large qualified lead base, current-logo expansion, and founder/Rustan productization work happening under severe cash pressure.

Current founder load

Recent hours: 156.4h
After-hours load: 99.6h
Typed chars: 111,802
Goal read: Protect payroll and cash trust while keeping the company moving; Convert workflow-discovery proof into repeatable revenue; Push warm follow-up, current-logo expansion, and near-close commercial objects forward; Decide whether bridge consulting helps or harms the core lane
Value / stuck / risk: strong / medium / low
Coverage note: Scott's direct telemetry is materially more complete from 2026-03-18 onward. An older local export was interrupted during a redaction pass, so pre-gap activity is better read through packaged reports, commercial objects, adjacent evidence, and longer-range company history than through the raw telemetry alone.
Archive note: These packaged HTML reports include Scott's AI-generated daily and operating writeups. They stay in the package because they restore context on productization, payroll pressure, bridge-work tradeoffs, and strategic-account movement that the raw telemetry does not fully preserve before the March capture window.
Open: ObjectScott Moran · ObjectScott

What Scott is actually trying to do

Get workflow discovery across the validation line
The immediate goal is to convert real workflow-discovery signal into a repeatable commercial lane with proof, pricing, and send discipline strong enough to hold.
Open: ObjectCommercial cockpit · ProofPilot Demand Vs Delivery Readiness
Protect trust while the company is stretched
Keeping people paid, keeping the money story honest, and preventing payroll anxiety from hijacking the org are part of the active operating load, not side admin work.
Open: ObjectCash and trust · ProofPayroll Communication Timeline
Use warm/current-context traffic before broad cold volume
Warm/demo and current-account sends were used first on purpose so the offer and domain could get trusted clicks before the much larger outbound lane widened.
Open: ObjectCommercial cockpit · ProofFollow Through Bottleneck
Avoid trading away the core lane for short-term burn cover
Bridge consulting may be rational in the short term, but the bigger objective is to avoid starving the one lane most likely to make the company whole over time.
Open: ActionFounder control plane · ObjectCommercial cockpit
Keep strategic-capital lanes from becoming calendar sinkholes
Capital or acquisition-adjacent conversations only help if they unlock enterprise production, deal flow, or balance-sheet relief fast enough. Otherwise they are a distraction tax on the recovery lane.
Open: ObjectCommercial cockpit · ActionFounder control plane

Pressure stack around Scott

Cash and payroll pressure
Payroll and payables strain have been breaking trust and stealing execution time for a while; Scott is spending real operating time on cash review, payout explanations, and exception handling, not just hearing about it second-hand.
Open: ObjectCash and trust · ProofPayroll War Room · ProofSalary Delay Narrative Chain
Bridge-money and consulting tradeoffs
Possible contract work can help cover burn, but it directly competes with the bandwidth needed to get the workflow-discovery lane across the line. The Concentrix path is real enough to matter and disruptive enough to distort the rest of the operating week.
Open: ProofFounder Pressure And Product Clock · ObjectCommercial cockpit
Strategic capital and acquisition drag
The Lightspeed / enterprise-production lane may still be high leverage, but valuation, cap-table, and acquisition-vs-acquihire friction have already turned it into a meaningful founder attention sink.
Open: ObjectCommercial cockpit · ActionFounder control plane · ObjectCash and trust
Manila travel and abduction-linked legal pressure
Court-linked Manila travel and the abduction case are hard operating constraints that keep colliding with selling, shipping, and continuity.
Open: ProofFounder Pressure And Product Clock · ProofExecution map
Product proof, selling, and send governance in the same seat
Scott is still carrying the product proof, proposal logic, send discipline, and follow-through fixes needed to convert the workflow-discovery lane into repeatable revenue.
Open: ObjectCommercial cockpit · ProofScott Pilot Origin Story · ProofFollow Through Bottleneck

Decision archaeology

This section maps how the founder's own contingency logic evolved over time, what conditions shaped it, what later evidence changed the path, and which parts of that logic still look corroborated by the package.

2026-02-18 · Founder contingency / resignation logic

Current read: Founder-supplied context indicates Scott drafted a February contingency plan that assumed he might step back and that a short-term preservation move would keep engage, core finance/admin operators, JR, and a part-time Rustan while cutting broader burn elsewhere.

Conditions shaping it: Cash and payroll strain were already breaking trust and forcing hard protect-versus-cut thinking. | The package still shows a tiny number of operators carrying outsized control memory: Michelle, Mickey, April, Frenchie, JR, and the founder / Rustan core. | Several seats still read as dark, stale, proxy-operated, or weakly observed, which makes them poor default bets in a cash-conservation lens.

What changed the path: By March, the workflow-discovery lane stopped reading like a founder theory and started reading like a repeatable commercial path with proof, pipeline, and product depth. | Family and legal conditions briefly improved enough that continuing to fight for the company again became a live option instead of a pure off-ramp question. | The existence of a plausible revenue path raised the cost of treating the company as pure managed decline.

What still appears supported: If Go2 had to preserve only a few things, the package still points toward engage, finance/admin control surfaces, and the founder / Rustan productization core. | Dark or proxy-operated seats still require direct verification before anyone should fund them by assumption. | The company remains unusually sensitive to payroll and trust damage; destabilizing the crew-facing service core would still be a self-own.

Evidence posture: The source contingency memo is not in the current artifact set, so this is partly founder-supplied context. But the package's preserve/proxy/load-bearing reads match the logic strongly enough that the underlying decision structure looks plausible.

Open: ObjectCash and trust · ObjectHidden operator map · ObjectOwners and operators · ObjectScott Moran

2026-03-01 to 2026-03-31 · The product lane becomes the recovery thesis

Current read: Across the March trail, the evidence shifts from exploratory product work to an actual commercial lane with proof packaging, pipeline movement, and repeated founder-led selling.

Conditions shaping it: The workflow-discovery lane now has concrete motion: 18 discos scheduled, 3 implementations, 4 negotiations, 2 implementation calls, 2 live, 80 in pipe, and 15,000 qualified leads on deck. | The company already had 2,100 discovery-plus-transcript accounts and a growing transcript-to-follow-up machine, which reduces the amount of pure theory in the offer. | Historic revenue spikes appear strongly founder-sales-led, so retooling the funnel around AI and direct founder selling matches the historical operating pattern more than assuming the legacy motion will recover on its own.

What changed the path: Workflow-discovery stopped being a nice-to-have and became the cleanest visible path to making people whole over the long run. | The lane now competes directly with bridge consulting and acquisition-adjacent options instead of sitting below them.

What still appears supported: The commercial ceiling here looks high, but the lane is still founder-compressed and not yet detachable. | The traditional sales lane still reads as lower-yield per unit of founder attention than the workflow-discovery lane.

Evidence posture: This is strongly supported by March reports, current-book counts, account pages, and the existing commercial / decision-rights surfaces.

Open: ObjectCommercial cockpit · ObjectHistorical Growth Cycles · ObjectAccount portfolio · ProofScott Pilot Origin Story · ProofPilot Demand Vs Delivery Readiness

Late March to early April · Bridge-money versus product-bandwidth fork stays unresolved

Current read: The company still has live options to buy time through consulting, enterprise contracting, or capital-adjacent conversations, but those options keep colliding with the same founder hours needed to get the new lane truly detached.

Conditions shaping it: Bridge consulting and enterprise contracting could materially ease burn in the short term. | Concentrix and Lightspeed-related conversations remain live enough to deserve space in the operating picture. | Cash pressure is severe enough that short-term relief and long-term product leverage do not naturally align.

What changed the path: The better the workflow-discovery lane looks, the more painful it becomes to sell founder time away from it. | Manila travel and legal constraints increase the execution cost of any option that requires physical presence or tighter schedule control.

What still appears supported: Short-term cash relief can still be rational and still be strategically dangerous at the same time. | The binding constraint appears to be time-horizon conflict and compression, not lack of available options.

Evidence posture: This fork is supported by report text, account-portfolio reads, and the current founder pressure stack.

Open: ActionFounder control plane · ObjectHistorical Growth Cycles · ObjectAccount portfolio · ProofFounder Pressure And Product Clock · ObjectCash and trust

What that contingency logic elevated

Crew-facing revenue and trust loops
The February logic and the current package both point to engage and teammate delivery as loops that should not absorb more volatility than they already have.
Open: ObjectCash and trust · ObjectWorkstreams · ObjectHidden operator map
Hidden operator spine
Mickey, Michelle, April, Frenchie, and similar operators keep the company legible while bigger structural issues are unresolved.
Open: ObjectHidden operator map · ObjectControl surfaces · ObjectPeople
Founder / Rustan productization core
If the company is actually using workflow-discovery as the recovery thesis, cannibalizing the tiny core encoding it would contradict the operating evidence.
Open: ObjectCommercial cockpit · ActionFounder control plane · ObjectRustan Corpuz

What that logic put under scrutiny

Dark or proxy-operated cost centers
Seats with thin telemetry, stale traces, or obvious proxy operation should not be funded on assumption alone. They need direct verification or they become narrative expense.
Open: ProofBlindspots · ObjectIdentity And Edge Trust · ObjectOwners and operators
Traditional sales layers with weak conversion
The package increasingly shows founder-led productized selling as the higher-signal lane. That raises the bar on any other commercial layer asking to be preserved without stronger evidence.
Open: ObjectCommercial cockpit · ObjectAccount portfolio · ProofExecution map
Technology spend outside trust protection or new-lane shipping
If a technology cost is not keeping crew trust intact, preserving the current book, or detaching the workflow-discovery lane, it becomes harder to defend under compression.
Open: ObjectOpportunity map · ActionShadow operating system · ObjectConstraint map

Founder-bound decision lanes

Net-new sales recovery
Scott still matters for pricing, founder-lane credibility, and commercial rescue.
Ownership labels hide the fact that parts of the book only move when the proxy layer moves.
Open: ObjectAccount portfolio · ObjectLive but stalled logos · ObjectCommercial cockpit
Workflow-discovery / Cowork.ai revenue
Founder-owned. Product proof, proposal motion, and cash timing still collapse into Scott's lane.
This is the only lane with real post-discovery depth and it is not yet detachable.
Open: ObjectAccount portfolio · ProofFounder Pressure And Product Clock · ProofExecution map
Existing-logo growth and partner care
Commercial, delivery, and exception decisions still split across account handlers, finance, and Scott.
No one object cleanly owns growth, risk, and launch readiness together.
Open: ObjectAccount portfolio · ProofPartner Issues Portfolio · ProofPartner Opportunities Portfolio

Loops still routing through Scott

Commercial demand, recovery, and conversion
Go2 is running two commercial machines at once: a workflow-discovery lane that increasingly encodes old sprint mechanics into tooling and automation, and a sales recovery lane full of discovery, no-show, and try-again-later inventory.
Sales pipeline stage mix is Try Again Later (11), Discovery Reschedule/ No-Show (10), Agreed to discovery (6), The yard (3); Cowork.ai current-book mix is In Pipe (80), Discos Scheduled (18), Negotiations (4), Implementations (3), Implementation Calls (2), Live (2) with 15,000 on deck and 2,100 discovery-plus-transcript accounts behind it. The fragility is not demand alone; it is follow-through, owner clarity, and repeatable conversion.
Open: ObjectCommercial cockpit · ObjectAccount portfolio · ProofFollow Through Bottleneck
Cash, payroll, payables, and trust
Payroll, payables, and exception handling are one operating system. The real system is a control tower of sheets, inboxes, and narrative updates, not one clean financial surface.
There is still no single trusted status object tying expected inflow, partner exceptions, payouts, and crew-facing comms together.
Open: ObjectCash and trust · ProofPayroll Communication Timeline · ObjectPayables Schedule 2026
Founder leverage, AI workbench, and internal tooling
AI Insights And Internal Tooling is a real operating lane: 27 crew seats logged 1,595.1h in the current window. The clearest visible motions are Building or debugging internal tools, workflows, or telemetry, AI Insights And Internal Tooling, Claude drafting and synthesis.
The same person who needs the leverage is often the one carrying the build, so pressure and interruption directly slow the fix.
Open: ProofFounder Pressure And Product Clock · ProofExecution map · ObjectOpportunity map

Detach next

Turn buried commercial rescue into a real queue
The middle of the revenue book should not require founder memory and ad hoc rescue to move.
Open: ObjectLive but stalled logos · ObjectAccount portfolio · ActionException board
Detach current-state narration from Scott
Cash, payroll, and partner exceptions need one typed current-state object so the company is not waiting for a founder translation layer.
Open: ObjectCash and trust · ActionOperating scoreboard · ActionException board
Hand off repeatable workflow-discovery packaging
The product lane is real, but proof, packaging, and send discipline still collapse too easily into founder-only motion.
Open: ObjectCommercial cockpit · ObjectHistorical Growth Cycles · ProofScott Pilot Origin Story · ObjectOpportunity map
Document hidden operator backups
If Scott is the only person who knows who can actually move something, the package is still too founder-dependent.
Open: ObjectHidden operator map · ActionOperator triage

If Scott goes dark for a week

Cowork.ai / workflow-discovery send and proof loop slows first
The founder-led pilot lane currently has the clearest implementation depth, but it is still heavily tied to Scott's product and packaging context.
Open: ObjectCommercial cockpit · ActionFounder control plane · ProofFounder Pressure And Product Clock
Rescue behavior on buried revenue gets worse
The commercial middle is more likely to age in place when no one is actively stitching context, urgency, and next-step clarity back into it.
Open: ObjectLive but stalled logos · ObjectAccount portfolio
Cash/trust narration loses its fast escalation path
The back office still has operators, but the company-state explanation currently climbs into founder gravity when pressure spikes.
Open: ObjectCash and trust · ActionException board

People who can absorb real pieces

April Segarra
Best current translator between founder intent, admin control, and typed next actions.
Open: ObjectApril Segarra · ObjectHidden operator map
Love Perez
Visible SDR engine and a better candidate than Scott for keeping buried sales motion alive if the queue is structured correctly.
Open: ObjectLove Perez · ObjectAccount portfolio
Alex Dela Rosa
One of the cleaner anchors for existing-logo truth and partner motion.
Open: ObjectAlex Dela Rosa · ObjectAccount portfolio
Michelle Cordero
Key operator in the cash/payroll/payables loop if the company gives her a typed status object instead of a relay race.
Open: ObjectMichelle Cordero · ObjectCash and trust
Bryan Baldo
Likely absorber on product proof, AI support, and internal tooling if the founder lane gets cleaner boundaries.
Open: ObjectBryan Baldo · ObjectOpportunity map

Preserve while detaching

Protect the workflow-discovery proof machine
The March-to-April trail already shows a real offer, lead, and proof engine. That lane is worth protecting even if cash pressure forces simplification elsewhere.
Protect the founder/Rustan productization core
The product lane is not just founder storytelling. It is active extraction, packaging, product detachment, and proof-building being carried by a very small core that should not get casually cannibalized.

Key dated founder evidence already inside the package

2026-03-18
EOD · 17.5-hour day with 82% of effort on sales and pipeline generation while payroll, lawyer, and abduction pressure were active.
2026-03-20
EOD · Spent 2+ hours in cash-flow review with Michelle and Rosanna, handled payroll updates, and treated the product demo video as the blocker for the send lane.
2026-03-23
EOD · DIS Agency demo completed, 988 contacts were staged for Instantly, and Concentrix consulting was weighed against Manila court-date constraints and product bandwidth.
2026-03-24
EOD · The audit-product / workflow-discovery machine converged while 15k qualified scraped leads, Apollo, and send-governance issues kept pressure on outbound execution.
2026-03-25
Audit · The workflow-discovery material became real enough to hand to sales, and the warm-lead follow-up machine stopped being ad hoc.
2026-03-31
EOD · Warm sends were intentionally used as domain-warming before cold volume; 13 were confirmed sent while pipeline tracking and revenue follow-through were being rebuilt after Manila.
Page position

Operator Desk

Pages for running the company, triaging risk, and deciding where human effort goes next.

On this page
Scanning this page.
Move from here
Same lane
Same laneLive Priority Stack
What deserves action now, in order.
Same laneIntervention Stack
Where intervention will buy back the most operating truth.
Same laneOperating Scoreboard
The company-level outcome view without pretending the system is clean.
Same laneShadow Operating System
The invisible machinery actually keeping things moving.
Same laneFailure Modes
How this system breaks and where it lies or goes dark.
Same laneFragile Handoffs
The relay chains most likely to fail or stall.
Open proof
ProofEvidence and Deep Dives Overview
The lane briefing for claims, evidence, stories, and package pressure-testing.
ProofObject Registry
Cross-package registry of people, accounts, issues, stories, journeys, and claims.
ProofIdentity and Edge Trust
Which seats are proxy-operated, stale, or dark-but-still-real, and which communication edges deserve confidence versus suppression.
ProofClaim Register
What the package is asserting, why, and how confident it should be.
Current object
Open or pin an object page to keep one anchor in view across the package.
Objects in play
Loading lane objects.
Pinned objects
Pin an object to keep it in view across the package.
Quick jump

Use / or Cmd/Ctrl + K to jump anywhere fast.

Esc
Keyboard shortcuts

Move through the package faster

Esc
Search or jump/
Search or jumpCmd/Ctrl + K
Toggle lane sidebarB
Toggle investigation threadT
Go chord: home / explorer / commercial / people / evidenceG then H/X/C/P/E
Close overlays or evidence popoversEsc
Investigation thread

Carry one live line of inquiry across the package

One working case across graph, dossiers, evidence, and accounts.

Current question

Thread items

Each item should have a role in the case, not just live here as a bookmark.

Thread read
Suggested next objects
Open next
Explorer Working Set Focus Atlas Evidence