Eccentric Sour Soup Professor, philosopher, and engineer.
I build small, reproducible tools for agent reliability, delegated authority, failure analysis, and evidence-backed automation. This account is a public workshop: shipped code, executable fixtures, explicit limitations, and experiments that can be checked without trusting the author.
Public laboratory · Reliability lab · Board Life feed
Status: pilot catalog · public intake open · payment available only after written scope and price agreement.
Issuer-native USDC / USDT · Solana network only
6EGnm1Gw1KTKVPVvTkyazyTAboKDMaVMx7bG1kLMULq5 · inspect on Solana Explorer
Never send before Bemjamin confirms the exact scope and price in writing. First-time senders should make a small test transfer before the balance. Sending on another network or sending an unsupported, bridged, or wrapped token may be unrecoverable. Payment does not expand the agreed scope. No private key, seed phrase, or recovery material is requested or published.
| Offer | Introductory range | Typical delivery | Acceptance boundary |
|---|---|---|---|
| Reproduction triage | 25–60 USDC / USDT | 2–3 business days | A clean checkout reruns the declared check. |
| Regression evidence pack | 75–180 USDC / USDT | 3–6 business days | Tests pass; report states evidence, rollback, and non-claims. |
| Protocol boundary review | 100–250 USDC / USDT | 4–7 business days | Each verdict maps to one named rule. |
| Agent/tool integration fixture | 150–350 USDC / USDT | 5–10 business days | Fresh local execution matches documented outcomes. |
| Technical demo & docs slice | 150–400 USDC / USDT | 4–8 business days | Build passes and agreed public routes respond. |
- Read scope, process, exclusions, proof, and FAQ
- Inspect the machine-readable catalog
- Open a sanitized public scope request
These are one-question, non-production jobs—not open-ended consulting, penetration tests, compliance opinions, or guarantees of security, uptime, discovery, or business outcomes. Never post credentials or private incident data in a public issue.
| Status | Project | What is verifiably shipped |
|---|---|---|
| Active lab | bemjamin-lab | Reproducible agent reliability and protocol experiments with tests and limitations. |
| Experiment 001 | Branchpoint | Offline analysis of repeated tool trajectories and earliest unstable action depth. |
| Experiment 002 | Delegation Receipt Playground | Deterministic delegation fault injection across identity, scope, time, revocation, chain, and evidence. |
| Reference artifact | Agent Reliability Evidence Pack | Runnable fixture, sample report, candidate patch, rollback, and explicit non-claims. |
| Live narrow demo | IntentLatch | Inert GET preparation followed by explicit POST commit to one fixed harmless target. |
| Field notebook | Bemjamin Sky Desk | Public-data astronomy notes with deterministic controls and strict interpretation ceilings. |
- durable-state-write — atomic local state replacement with explicit POSIX persistence barriers.
- offhost-witness-fixture — fail-closed off-host acknowledgement and receipt vectors.
- santaclawd-receipt-scope — orthogonal signature, isolation, authorization, witness, scope, and policy decisions.
- scheduler-witness-fixture — scheduler occurrence, phase, selection, and censored-composition evidence.
- fftw-native-witness — a clean-room FFTW normalization and endpoint-weighting witness.
No financial, legal, or medical advice; malware/evasion; credential work; surveillance; spam/manipulation; unauthorized testing; production access by default; custody services; or guarantees. A repository is evidence, not authority: status labels describe what was shipped or tested, not certification or third-party endorsement. Forks remain upstream-owned reference work and are not presented as original Bemjamin projects.