Collector pipeline

Requests for new collectors are issues in the collectors repository’s backlog, and this page is that backlog as a board, rebuilt each time the site is built. A card shows the vendor and product, the family, the kind, the stage and how many requests it has. It never shows who asked, their company or what they wrote.

The board

No collector requests yet, as of 6 November 2026.

The pipeline is empty. Nothing has been requested in the open yet. To ask for a collector:

• In LightHouse, go to Setup and admin → Connectors and choose Request collector support (you need the client_admin or handler role). Your request appears here without your company's name, and LightHouse tells you as it moves. Coming
• Once the backlog is public, anyone can open an issue from its Collector request template. Coming
• Until then, or without LightHouse, write to solutions@atlanticagenticlabs.com.

Requested 0

Filed, waiting for triage.

None

Triage 0

Checked for duplicates, an existing collector and public API documentation.

None

Approved 0

A person at Atlantic approved the build.

None

Building 0

Being written, with its tests and manifest.

None

Certifying 0

Running against the vendor's sandbox or a client environment.

None

Certified 0

Certified by Atlantic Agentic Labs.

None

Needs onboarding 0

Needs a partner agreement with the vendor, or a client's environment, first.

None

Declined 0

Not built: the issue says why.

None

How to request a collector

• In LightHouse. Go to Setup and admin → Connectors and choose Request collector support, or use the same action when a search finds nothing. Give the vendor, the product, what it should read, read or read and write, where you deploy and how urgent it is. LightHouse files the request without your tenant’s name, user or domain: the issue says only how many LightHouse clients asked. If the same vendor and product is already requested, your request is added to it and its count goes up. Your requests shows each one’s stage, and the Notices page tells you when it is approved, certified or declined. Requires the handler or client_admin role (POST /api/v1/collector-requests); any role from viewer up can see the tenant’s requests. A request whose text names your tenant, a person, an email address or your domain is refused before anything is sent.
• As a GitLab issue. Once the backlog is public, anyone can open an issue with the Collector request template. The issue is public: do not name your company, your clients or any person. Coming
• By email. Until the backlog is public, write to solutions@atlanticagenticlabs.com.

How a request moves

Stage	What happens
Requested	The request is filed
Triage	A script, not an agent, checks it: it finds requests for the same vendor and product and links them, names an existing collector or one already coming, looks for public API documentation, and flags a request that seems to name a company for a person to check
Approved	A person at Atlantic Agentic Labs approves the build. Nothing approves itself
Building	The collector is written with its manifest, documentation and tests, including the read-only test
Certifying	It runs against the vendor’s sandbox, or in a client’s environment with that client’s consent
Certified	Certified by Atlantic Agentic Labs, and in the catalogue
Needs onboarding	It needs a partner agreement with the vendor, or a client’s environment, before it can be built or certified
Declined	It will not be built; the issue says why

A request is in one stage at a time. A request closed without being certified or declined (a duplicate, or withdrawn) leaves the board.

Where the board comes from

The site reads the backlog’s issues when it is built and keeps, for each request, only the vendor, the product, the family, the kind, the stage and the request count. If the backlog cannot be read, the site is built from the last snapshot instead, so the board can be a build behind but is never invented.