1–10 of 21 posts
Show HN: A working reference implementation of context engineering
github.com
I would have stuck a qualifier in there
Putting engineering after a term doesnt make it engineering.
I feel like AI is going to be doing all the fun stuff and I will just left organizing the data and docs it needs to generate code.
Putting engineering after a term doesnt make it engineering.
The “enforcement layer” is the hardest and most important part, and is barely addressed.
- is the answer structurally / syntactically valid?
- is it appropriately grounded and evidenced?
- is it accurate? In what ways does it fall short?
Each of these should be triggering an agent to rework and resubmit etc. or failing that a disclosure to the user about how the answer falls short and should be reviewed / remediated.
This feels like it’s from the era of trying to oneshot a good enough answer.
I feel like AI is going to be doing all the fun stuff and I will just left organizing the data and docs it needs to generate code.
Welcome to becoming a project manager.