Open Multi Agent Per-call tool gate hook
Added a typed gate between validated tool input and execution, with denial results and trace metadata.
Lint, unit tests, build, coverage, scaffold, package smoke checks.Scarab Diagnostics Suite
Evidence before implementation.
Scarab Diagnostics Suite helps teams understand the repair boundary before patching begins: where the failure belongs, what evidence supports the diagnosis, and what validation should prove the repair.
7 merged upstream PRs Accepted public pull requests across six upstream projects.
1 accepted enhancement Open Multi Agent merged a per-call tool gate hook from an enhancement-labeled issue.
1 feature PR in review QuantConnect Lean scheduled walk-forward optimization remains open and separate from accepted proof.
Public proof
Open Field LabMerged upstream work
SvelteKit Rejected streamed-data race
Moved stream rejection handling earlier in server data rendering so page catch blocks receive delayed failures.
Package checks, lint, focused Playwright regression in dev and build/preview.Docker Compose Config-variable validation boundary
Allowed variable discovery over non-interpolated Compose models without weakening normal config validation.
Focused regressions, package tests, lint, diff check.Shortened CAFS temp directory names to preserve Unix-domain socket path budget in package preparation.
Store, prepare-package, git-fetcher tests, compile, pre-push hook.Skipped dependency auto-install when a dependency-status check was intentionally skipped for no manifest.
Targeted Jest tests, TypeScript build, package lint.OpenAPI Generator Kotlin boolean const enum generation
Kept boolean enum values as boolean literals for OpenAPI 3.1 const output instead of quoted strings.
Targeted regression, full Maven reactor, sample regeneration, docs export.xdg-desktop-portal-wlr ScreenCast SelectSources default
Defaulted omitted ScreenCast source types to monitor capture while preserving explicit caller options.
Diff check, Fedora Meson/Ninja build, upstream Alpine/Arch/FreeBSD checks.Merged public PRs are evidence of accepted work, not project affiliation or maintainer endorsement. Open PRs, downstream-carried fixes, diagnostic findings, and explicit non-claims remain in the Field Lab.
Feature work in public review QuantConnect Lean: Scheduled walk-forward optimization support Field Lab record Open feature PR
Services
Start intakeChoose the level of review you need.
Diagnostic Boundary Report
A concise assessment of where the failure belongs and what evidence supports that diagnosis.
from $750 Best when a repository failure is real but the repair boundary is unclear.
Bounded Repair Candidate
A scoped repair path or patch candidate with validation notes and reviewer-readable limits.
from $2,500 Best when the failure is narrow enough to prepare a reviewable change.
AI-Assisted Change Review
An independent boundary and evidence review for AI-assisted patches before they move forward.
from $1,250 Best when a generated or assisted change needs technical review before adoption.
Corporate advisory
Custom Corporate Advisory
For broader organizational or multi-system work, we scope a custom engagement around the actual technical boundary.
Custom scope - engagements from $10,000 For teams dealing with multi-repo systems, AI-assisted development workflows, repository drift, or unclear ownership and validation boundaries. Engagements may include architecture and change-boundary assessment, AI-readiness review, repository governance, diagnostic workflow design, or support for high-risk software changes.
Minimum prices reflect a bounded public or private repository review. General turnaround is 24-48 hours depending on complexity. Nonprofit and community groups are quoted on a sliding scale.
Diagnostic Suite
What Scarab Diagnostics Suite brings to repository work
Boundary assessment
Scarab Diagnostics Suite separates where the failure belongs from where a patch happens to be convenient.
Evidence structure
Public-safe findings, issue links, PR records, validation notes, and non-claims stay attached to the work.
Validation planning
Repairs are judged downstream by repo-native checks: tests, builds, lint, typecheck, and focused regressions.
Request review
Send the scoped failure first.
Start with the diagnosis. Pay for implementation only when the boundary is clear.
- Describe expected behavior, actual behavior, and safe links.
- Private repository work begins with a high-level scope discussion.
- We confirm the right service and fixed scope before work begins.