Show HN: A working reference implementation of context engineering
21 points - last Friday at 6:20 PM
I've been presenting at local meetups about Context Engineering, RAG, Skills, etc.. I even have a vbrownbag coming up on LinkedIn about this topic so I figured I would make a basic example that uses bedrock so I can use it in my talks or vbrownbags. Hopefully it's useful.
I don’t really think this reflects the current era of challenges?
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.
slashdave
today at 12:08 AM
> the information an AI system needs to produce accurate ... outputs
I would have stuck a qualifier in there
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.
Putting engineering after a term doesnt make it engineering.
Software engineering is certainly not engineering. Even at the highest levels. Real engineering have infinitely more complex interactions in the physical world than symbolic institutions for machines.
slashdave
today at 12:43 AM
Probably just using the convention started by the term "prompt engineering", which is forgivable.
sroussey
today at 12:57 AM
not sure i forgive "prompt engineering"