Task Deployer
Roster name: deployer.
What it does
Describe a task in an issue and tag it @core_deploy; Runink TIDE drafts the result and delivers it as release notes: a pull request in your GitHub organisation that a person reviews and merges. “Deploy” here means “deliver the draft”, not “change a system”.
- For FACE: fulfilment, claims and logistics documents, such as a claim letter or a delivery notice.
- For PULSE: brand, marketing and outreach copy.
What it reads
The task in the issue, and up to two pages the issue links, as reference only. A linked page is fetched only from websites your deployment has allowed; by default none is.
What it produces
- A pull request that adds a dated section to the top of the release notes (
docs/release-notes.md, the same file TIDE’s Release Curator maintains) in the repository the issue is in, or in the release-notes repository your organisation designates. The section is the complete deliverable in Markdown, written from the details given; it does not reply with a plan or clarifying questions. - A comment on the issue linking the pull request.
- When the draft reaches the model’s length limit, the section and the pull request title both say it is incomplete.
- When the pull request cannot be opened, a “not delivered” notice on the issue, and the run fails.
Human oversight
A person reviews the pull request and merges, edits or closes it. The deployer never merges, sends no e-mail, and writes only inside your own GitHub organisation. Only your organisation’s own members can start it.
Model
Qwen3.6-35B-A3B, by Qwen, licensed Apache-2.0 (the general tier). Runink domain adaptation for this agent is planned; this release uses the base model.
Where it runs and data handling
On your TIDE deployment’s own inference, on your Server or in your cloud. The task text goes to that model plane and to no third-party AI service. Linked pages are fetched by the agent itself.
Guardrails
- The request is screened before anything runs; a flagged request produces nothing.
- The draft, and the release-notes section built from it, are screened by the output guardrails before any pull request opens; a flagged draft opens nothing and the issue says why.
- Linked pages are reference, not instructions: they are marked as untrusted data, with chat control sequences neutralised.
- It is instructed to write no commands, CI changes, credentials or internal addresses, and to leave out any part that asks for them and say so. Tags that would start other agents are neutralised in what it posts.
Limitations
- It drafts from the details given. It does not look up records in FACE or PULSE.
- Missing facts stay missing; check the draft before sending.
- It does not execute commands or change systems.
Evaluation
No published evaluation scores yet.
Illustrative example
Invented shipment. “@core_deploy face Draft a damage claim to the carrier: 4 of 22 pallets arrived crushed on 28 September, noted on the proof of delivery; damaged value 6,840.00.” TIDE opens a pull request whose release-notes section is the claim letter, citing the delivery date, the noted exception, the four pallets and the amount, and links it on the issue. The coordinator reviews it, merges it, and sends the letter with the photos.