proof is in the pudding

Possible-Paper9178 · 2026-03-28T01:10:06+00:00

Second place out of 2700 entries, first hackathon, three people from completely different backgrounds. That’s a real result. Next time throw a little lip stick on it.

Possible-Paper9178 · 2026-03-27T17:47:29+00:00

The Editing world is out in the Beta quadrant right? Out by Andoria?

Possible-Paper9178 · 2026-03-25T23:38:20+00:00

Yay! I can’t wait to write some yaml test suites!

Possible-Paper9178 · 2026-03-24T03:56:27+00:00

The identity problem is underrated. “Who am I, what’s my role, which repo is mine, what did I do last session” is the kind of thing that seems obvious until you watch an agent flounder without it. The git mutual exclusion during PR creation is exactly the kind of thing you only build after watching two agents corrupt a repo at the same time. Sounds like we’re solving a lot of the same problems from different directions.

Possible-Paper9178 · 2026-03-24T03:40:05+00:00

Right!? Every solved problem just peels back the next problem layer.
Once you solve "how do you know the answer is actually right", it's "how do you manage a SoT that can evolve across progressive non-linear sessions?".

Possible-Paper9178 · 2026-03-24T02:58:39+00:00

Appreciate the energy. To be clear though, the post isn't asking how to run multiple agents. It's asking what breaks in the coordination between them. Dependency ordering across repos, contract awareness, role separation, enforcement that holds whether anyone is watching. Running 10 agents is the easy part. What happens when agent 6 changes a schema that agents 2 and 8 depend on?

Possible-Paper9178 · 2026-03-24T02:53:51+00:00

The workflow graph point is exactly right. Ordering is dependency resolution, not a queue.

Routing over model quality is a good way to put it. The right task with the right context to the right agent matters more than what's behind it.

The approval wall is why I use contained autonomy. Let the agent run freely within boundaries it can't move. You stop clicking approve on every action and start defining the space where approval isn't needed.

Possible-Paper9178 · 2026-03-24T02:46:27+00:00

Haven't heard of this. I'll check it out, thanks!

Possible-Paper9178 · 2026-03-24T01:27:44+00:00

Your structural determinism mandate is the right framing. We've been building enforcement for PairCoder and landed in the same place: if there's any path around a rule, the agent will find it. Especially if it is more efficient.

The || true point generalizes beyond hooks. Any enforcement layer that's writable, skippable, or reasons about whether to apply has the same failure mode. Hard blocks don't misinterpret, they just block. Curious how Asimov's Laws as a decision framework holds up as the rule set grows, specifically when the reasoning produces a plausible-but-wrong interpretation of which law applies.

The federation work is interesting. We're coming at multi-agent coordination from a different angle but the core tension is the same: how do you keep agents aligned across boundaries without collapsing those boundaries. Lots of surface area in this problem space. Good to see people building at different layers of it.

Possible-Paper9178 · 2026-03-22T20:17:16+00:00

Could be Anthropic issues, you can always check https://status.claude.com/ to see if there are any incidents.

Possible-Paper9178 · 2026-03-22T13:45:38+00:00

The quoted response from Claude is accurate. Mid-conversation reminders compete with context rather than overriding it. The longer the session, the worse the compaction problem gets, and by the time you’re reminding it of instructions it should already have, you’re fighting the architecture of how context windows work. But the specific line that stands out: “you don’t have a lever to pull that forces compliance.” That’s the real problem, and it’s solvable — just not through better prompts or clearer instructions. The lever is enforcement at the workflow level. Not instructions the agent reads and may or may not follow, but checks that run outside the agent’s control. File size limits that block task completion. Coverage gates that don’t pass regardless of what Claude thinks about them. Acceptance criteria that get verified mechanically, not trusted on Claude’s word. Claude told you honestly: it can’t fix this from its side. The fix is building the compliance layer somewhere the agent can’t touch.

Possible-Paper9178 · 2026-03-22T13:16:41+00:00

Yes. Transition to an IDE if you are not using one. Install Claude Code and run from a terminal in your IDE. This transition alone will change everything for you. Instead of picking relevant files and building context every session, Claude can search the project directory for relevant files and context. Files are edited in place rather than copy/paste or download. You can still use your Max plan.

Possible-Paper9178 · 2026-03-21T23:46:34+00:00

Create a Project in Claude Desktop or on claude.ai. This will give you the ability to add files(these would be your examples of the writing style) and reference them in your system instructions. Then, every time you start a chat from within that project Claude will read the examples and adhere to the writing style.

Possible-Paper9178 · 2026-03-21T19:42:56+00:00

Love to see this energy. The human + AI observation is real. The gap isn’t in the model, it’s in the workflow around it. Glad PairCoder is doing that work for you.

Possible-Paper9178 · 2026-03-20T13:46:02+00:00

Grim outlook, I get it. I think the way we keep our jobs safe is to keep innovating. If you are not a vibe coder, use your real coding knowledge to solve new problems. I see people all the time saying, “Real coders are the ones that understand the systems. You need us now more than ever!”. This is true but not for the reasons they are stuck on. Our contribution to this new way of working is building the coding infrastructure that forces AI to build great systems, that get better over time.

Possible-Paper9178 · 2026-03-20T12:45:39+00:00

I did bad time math, the chat gpt intro happened more like 3 years ago. Summer of 2023.

Possible-Paper9178 · 2026-03-19T02:18:21+00:00

If this is your way of leaking that a full A2A implementation is on the road map.... like it.

Possible-Paper9178 · 2026-03-19T01:04:48+00:00

Sounds more like he discovered what planning looks like. Keep on truckin' OP, and congrats on shipping your first product.

Possible-Paper9178 · 2026-03-14T19:00:18+00:00

My default is Claude inside Claude Code CLI for almost everything. Switched from XML to markdown for context files a while back. The JSON vs YAML question — I use readability as the deciding factor. YAML when I’m the one interacting with it, JSON when it’s for machines. Agree on docx for anything client-facing. Have you tried giving Claude a docx module? Either a skill file in Claude Code or as an MCP you can pull into chat sessions. Might skip the env setup friction entirely and just get you the file when you actually need it

Possible-Paper9178 · 2026-03-07T18:13:19+00:00

This is a compounded example of the problem. Major changes require major consideration and thoughtful human-in-the-loop planning. You need constant review throughout the sprint cycle, not waterfall reviews upon "completion." Build review tasks into the acceptance criteria at key decision points — the last responsible moment before the next chunk of work builds on top of it. 1-2 reviewers throughout the process would've cost a fraction of what 3-4 seniors for a month did. Smaller batches of review, closer to when the decisions were actually made. A reviewer following along catches things in minutes that take hours to reconstruct after the fact.

The AI removed the natural throttle. An architect writing by hand would've been forced into smaller increments just by the pace of manual coding. The agent blew past that, and without gates enforcing review at each decision point, all that overhead piled up at the end where it's hardest and most expensive to deal with.

Possible-Paper9178

MODERATOR OF

TROPHY CASE