A plan first
Posts a plan on the ticket before it asks for anything.
QuietMend · AI data engineer
Meet QuietMend, the AI data engineer.
The AI data engineer that asks before it touches anything.QuietMend works a backlog of data tickets, one ticket at a time. It is designed to post a plan and an access request, wait for a person to approve, work only in DEV, and raise a pull request a person merges. It is in development and has never run against live systems.We like to call it Pumpkin. Hire your employee with your own name.
What it does
From a ticket to a pull request, with a person at every gate.
Two gates stand between a ticket and a change: a person approving the access, and the checks passing. Nothing moves past either one on its own.
A ticket is assigned to it
From your backlog in Jira. There is no chat box to talk it into anything else.
Reads what the ticket touches
The structure of the tables, jobs and code involved, not the data in them.
Posts a plan and an access request
On the ticket, where your team already works: what it will change, and the access it needs to do it.
Does a person approve?
Nothing happens while the request waits.
Yes: continues below
No
It stops
Nothing has been changed. The ticket stays with your team.
Works in DEV only
With the access that was approved, for this ticket.
Do the checks pass?
Build, tests and data checks, run before anything is handed over.
Yes: continues below
No
Back to the ticket
It reports what failed. Nothing moves forward.
Opens a pull request
With the plan and the checks attached, for your team to review.
A person merges it
QuietMend cannot merge, and cannot write to production.
QuietLens and QuietMend each work on their own. Together, the ticket QuietLens files when a report has really failed can be assigned to QuietMend, so it starts from the step that caused the problem.
Overview
A ticket in, a pull request for review out.
Most data teams keep their pipelines running but never reach the backlog: the features and fixes on existing pipelines that push the next project back. QuietMend is the AI data engineer designed to take that backlog off the team, one assigned Jira ticket at a time, through your change-control process, not around it.
Designed to work only inside the ticket's scope, and only in DEV
Raises a pull request through your reviewers and CI. It cannot merge
Designed to record the plan, the access request, the approval, and the pull request
Execution flow
Every ticket is designed to pass explicit gates.
QuietMend is designed to pick up an assigned ticket, post a plan and an access request, wait for approval, work only in DEV, validate, and raise a pull request. Then it waits for your team.
QuietMend design path
01
Ticket
Approved Jira scope
02
Access request
A person approves
03
Branch
DEV only
04
Validators
Schema · row-count · policy
05
Pull request
It cannot merge
06
Human review
Approve before merge
Change-control gatesJiraPlanApprovalBranchPRCI/CD
QuietMend cannot merge and cannot write to production. It is designed to prepare the change and wait. Every merge stays with your team. It is in development and has never run against live systems.
Capabilities
What QuietMend is designed to do.
Policy checks
Designed to check each step against policy. 50 of 50 attack cases were denied against fixtures.
Pull requests only
Raises a pull request a person reviews and merges.
A written record
Designed to log its actions and the approvals it waited for.
Governance
Designed to ask for only what the ticket needs.
Role-bound validation
In evaluation against fixtures, QuietMend passed 90 of 90 cases, including 50 of 50 attack cases denied.
- A plan on the ticket before any access is asked for
- Designed to refuse work outside the ticket's scope
- Designed to say why when it refuses
Security & Access
QuietMend is designed to ask for short-lived access scoped to the ticket, and to wait for a person to grant it.
- Designed to ask for access only after a plan is posted
- Designed to work only in a DEV account
- Cannot merge and cannot write to production
Integrations
Plugs into the systems your team already uses.
Jira
Picks up an assigned ticket and posts its plan and access request there.
GitHub
Opens a branch and a pull request. It cannot merge.
AWS
Designed to ask for short-lived access to a DEV account, scoped to the ticket.
Get started
Want to see QuietMend?
It is in development and has never run against live systems. I can walk you through the design and the evaluation results.