ENGINEERING
Daily HuggingFace license drift scan that files Linear issues
Runs every morning across all your tracked HuggingFace models, detects any model-card license that changed since yesterday.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionLoad model-to-repo mapPostgres
- ActionFetch each model card licenseHugging Face
- LogicFilter to licenses that changed since last snapshot
- ActionOpen a Linear issue per changed modelLinear
- OutputPersist new license snapshotsPostgres
What it does
This workflow is a scheduled sweep over every HuggingFace model your organization depends on. Once a day it snapshots each model card's license, diffs it against the previous snapshot, and for every license that moved it opens a Linear issue assigned to the owning team. The issue includes the model name, the old and new SPDX license, and a link to the affected repos so triage is one click away.
When to use it
Use it when models are pinned across many repos and you want a single proactive backstop rather than per-PR checks. It catches license changes even on models you haven't bumped recently, which is exactly where surprises hide.
How it works
- 1A daily schedule fires the workflow.
- 2It loads the full model-to-repo map from Postgres.
- 3It fetches each model card's current license from HuggingFace.
- 4A branch filters to only models whose license differs from the stored snapshot.
- 5For each changed model it creates a Linear issue tagged to the owning team with old/new license details.
- 6It writes the new license snapshots back to Postgres for tomorrow's comparison.
Set it up
What you configure once, before turning it on.
- 1Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
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.