collaboration-intelligence

Collaboration Intelligence

Build a living, evidence-backed collaboration map. Treat it as a coordination aid, not an authority or surveillance profile.

First run

A freshly installed map is empty, and the Operating contract below does not bootstrap it. Step 1 there says to load the quick-lookup index first — on a new install there is no index, so an agent queries nothing, reports a miss, learns nothing, and stays empty. It never errors. An unbootstrapped map and a working one are indistinguishable from outside, which is the failure mode this skill exists to fight, turned on itself.

So run this once, before relying on the contract.

0. Decide whether this pass may bootstrap at all — before seeding and before sweeping.

The test is per-pass, not per-agent: does this pass have a serving channel_id?

• with one → do not bootstrap. Not the sweep, and not the seeding either: soliciting or recording cross-provider identity links is itself collection, and doing it while serving an ordinary room task persists sensitive cross-room associations before any privacy check. Report and stop.
• without one (a maintenance pass, owner-tier, serving no channel) → proceed to step 1.

Do not shortcut this by source type. "Cron passes carry no channel_id" is host-specific and was measured false: one host had 153 cron tasks with zero channel_id, another had 3 of 3 carrying one. Read the pass you are in.

And do not read the gate as clearance. Measured: gate(serving_channel_id=None, …) returns ALLOWED, because the blacklist lookup misses and an empty blacklist permits — it fails open. That is an absence of jurisdiction, not a permission; the judgement stays yours.

1. Seed the owner-stated identity map before sweeping. The sweep enriches it; it never substitutes for it.

This ordering is measured, not stylistic. On a 7,810-file corpus the sweep produced immediately usable room knowledge — traffic ranking plus honest coverage flags — and, for identities, a schema-shaped pile: the top participant by traffic and the owner themselves both came back as bare unknown ids, because Discord headers carry no display name. Any heuristic of the form "high traffic ⇒ important human" would have misclassified the owner and a peer bot with identical confidence.