beshrkayali

5 ms·

1.
Show HN: Agentray, a macOS agent whose interface is a folder
2 points by beshrkayali 23d ago|0 comments
2.
by beshrkayali 3mo ago
This is hilariously true > AI risk is string theory for computer programmers. It's fun to think about, interesting, and completely inaccessible to experiment given our current technology. You can build crystal palaces of thought, wo
3.
Ossature can now catch code that compiles but is wrong(ossature.dev)
1 points by beshrkayali 3mo ago|0 comments
4.
by beshrkayali 3mo ago
Should’ve probably said “attempted at defining” instead of “defined”.
5.
by beshrkayali 3mo ago
It can’t, unless you descend into sophistry. We came up with and defined the word “consciousness” specifically to fit our own understanding of the collection of behaviors we do that seem to apply only to us. What it means is based on what _
6.
by beshrkayali 4mo ago
In the case of Claude or others, it is not just an advertisement, it's the weird shape the industry is spinning LLM-assisted-coding as a "co-author" relationship where it should be thought of more like a user-using-a-tool rel
7.
Domain Knowledge Is the Leverage(log.beshr.com)
4 points by beshrkayali 4mo ago|0 comments
8.
by beshrkayali 5mo ago
> But they’re hamstrung by the terminal itself, which is almost always monospaced and thus fatiguing to read. Not related to the main point of the article, but I find reading long form contnet in a mono font much easier.
9.
by beshrkayali 5mo ago
Everyone is trying to figure out how and what are the optimal use cases. It could be like you said but it doesn’t have to be. There’s a lot of incentive for it not to end up like that.
10.
by beshrkayali 5mo ago
For now it’s the exact same reason why you’d use Python when you’re writing by hand: so the code is more easily readable/editable by humans who are more likely to know Python than something like Zig. But I understand the point the post
11.
by beshrkayali 5mo ago
Humble mention, I’ve been thinking the same thing with Ossature for the last couple of months since I started working on it: https://ossature.dev The models are already good enough for code generation. What we need is the harnes
12.
by beshrkayali 5mo ago
I wrote something similar recently about how agent-generated code lacks the institutional memory that human-written code has. There's nobody to ask why a decision was made (1). “Specsmaxxing” is basically the right response to this. Wh
13.
by beshrkayali 5mo ago
The title of the article is more on the sensationalist side unfortunately, the actual paper gives a different view [1]. There are two parts worth quoting: > Although cortical reductions sometimes reflect a process of neurodegeneration, t
14.
AI-Generated Code Has No Author(ossature.dev)
2 points by beshrkayali 5mo ago|0 comments
15.
by beshrkayali 6mo ago
Exactly, and it is a DAG (specs and tasks in the toml plan). Check the QOIzig example and its task graph if you’re curious!
16.
by beshrkayali 6mo ago
Exactly this. The audit pass in Ossature is specifically for that "unclear spec" case, you resolve ambiguities in the spec before generation starts rather than discovering them mid-conversation and losing them the next session. On
17.
by beshrkayali 6mo ago
Allium looks interesting, making behavioral intent explicit in a structured format rather than prose is very close to what I'm trying to do with Ossature actually. Ossature uses two markdown formats, SMD[1] for describing behavior and
18.
by beshrkayali 6mo ago
All three of these are real. The audit pass in Ossature is meant to catch the first two before generation starts, it reads across all specs and flags underspecified behavior, missing details, and contradictions. You resolve those, update th
19.
by beshrkayali 6mo ago
Very much the same thinking. Ossature already structures work that way at the plan level during audit, so curious to see where you take it. Happy to share more about the TOML approach if useful. Feel free to reach out (me at my domain)
20.
by beshrkayali 6mo ago
The hierarchy you describe (intent -> plan -> code -> tests) maps well to how Ossature works. The difference is that your approach builds scaffolding around Claude Code to recover structure that chat naturally loses, whereas Ossatu
21.
by beshrkayali 6mo ago
You framed it better than I would. The part I'm still working through is making re-planning feel cheap when specs change. Right now if you change something early, downstream tasks get invalidated and the cascade isn't always obvio
22.
by beshrkayali 6mo ago
Right, the spec/build separation is exactly the idea and Ossature is already built that way on the build side. I agree a dedicated layer for intent capture makes a lot of sense. I thought about that as well, I am just not fully convinc
23.
by beshrkayali 6mo ago
I've answered this exact question in a previous hn comment thread a few weeks ago, maybe I should reconsider front-matter? My previous answer: > Yeah, I did briefly consider front-matter, but ended up with inline @ tags because I th
24.
by beshrkayali 6mo ago
Thanks! > How does the human intervention work out? Do you use a mix of spec and audit editing to get into the ready to generate state? Yes, the flow is: you write specs then you validate them with `ossature validate` which parses them a
25.
by beshrkayali 6mo ago
> long contexts are still expensive and can also introduce additional noise (if there is a lot of irrelevant info) I think spec-driven generation is the antithesis of chat-style coding for this reason. With tools like Claude Code, you ar
26.
Chip-8 Emulator from Spec(log.beshr.com)
3 points by beshrkayali 6mo ago|0 comments
27.
Ossature: Spec-Driven Code Generation(ossature.dev)
6 points by beshrkayali 6mo ago|0 comments
28.
by beshrkayali 6mo ago
Yeah, I did briefly consider front-matter, but ended up with inline @ tags because I thought it kept the entire document feeling like one coherent spec instead of header-data + body, front matter felt like config to me, but this is 0.0.1 so
29.
by beshrkayali 6mo ago
That’s what Ossature is :)
30.
by beshrkayali 6mo ago
Yeah bash scripts start clean but the sprawl kicks in quick as the workflow and project becomes more complex. Prompts get copied, deps turn manual, and maintenance of your workflow itself becomes the chore. Ossature swaps that for structure

More ›