Starbuck reference workflow
Field Note: Approval-Gated Repository Change
A sanitized Starbuck workflow from repository question through evidence, patch preparation, checks, and explicit approval.
Key considerations
Context bounded
Approved repository and editor context enters the task.
Evidence retained
Files, artifacts, diffs, and checks remain reviewable.
Writes gated
The change does not become a pull request without approval.
Architecture at a glance
Constraint
The engineering workflow needed natural-language assistance without granting a model arbitrary host execution, secret access, package installation, or default-branch writes.
Read and plan
Starbuck gathered approved repository context, filtered unsupported or secret-like files, and produced a task plan with visible evidence.
Prepare and check
The isolated runner prepared a reviewable patch and recorded task events, changed files, artifacts, and check results.
Approve the boundary crossing
Repository writes, package work, network access, and pull-request creation remained explicit actions rather than implicit consequences of model output.
Field-note status
This sanitized Pulsar engineering reference workflow is paired with current real QA evidence showing a secret-scanned diff, branch state, and explicit approval boundary.
Private deployment consultation
Review Pulsar against your environment.
Bring the infrastructure, security boundaries, model runners, and use cases. The Pulsar team will map the appropriate deployment path.