ENGINEERING
Unknown-License Research and Approval Escalation
For dependencies whose license cannot be auto-classified, an agent researches the project's actual licensing online and routes a structured approve/reject request…
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: unknown-license package receivedHTTP webhook
- ActionResearch package license terms on the webBrave Search
- LogicBuild risk summary and recommendation
- ActionPost approve/reject request to SlackSlack
- OutputRecord decision and reply on the PRGitHub
What it does
Handles the hard cases the deterministic scanner cannot: packages with missing, ambiguous, or dual licenses. An agent searches the web for the project's real license terms, summarizes the risk, and asks a human to make the call from Slack with a single click.
When to use it
Use it as the human-in-the-loop fallback behind an automated license gate, so unclassifiable dependencies get a documented decision instead of silently passing or blocking a team for days.
How it works
- 1A webhook fires from the upstream gate whenever a package lands in the unknown bucket.
- 2An agent runs a Brave Search over the package's homepage, repo, and license files to determine the effective license and any dual-license terms.
- 3A logic step assembles a risk summary: license found, confidence, and recommended action.
- 4An action posts an interactive approval request to the engineering Slack channel with Approve and Reject buttons.
- 5The output step records the human's decision and replies back to the originating PR via GitHub.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect Brave SearchWeb, news, image, video search.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.