Pull to refresh

Show HN: A working reference implementation of context engineering (github.com)

by linsys 15 comments 46 points
Read article View on HN

15 comments

[−] rao-v 25d ago
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.

[−] linsys 24d ago
[flagged]
[−] dang 24d ago
[−] linsys 24d ago
My bad. Won't happen again.
[−] dang 24d ago
Appreciated!
[−] zihotki 25d ago
No numbers/measurements/benchmarks and you dare call it "a working" one? Any real proofs that this 'works'?
[−] linsys 24d ago
[dead]
[−] segmondy 23d ago
I like it, it's a good start.
[−] slashdave 25d ago

> the information an AI system needs to produce accurate ... outputs

I would have stuck a qualifier in there

[−] r4ge 25d ago
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.
[−] ayuhito 25d ago
Welcome to becoming a project manager.
[−] tmpz22 25d ago
Putting engineering after a term doesnt make it engineering.
[−] jryio 25d ago
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 25d ago
Probably just using the convention started by the term "prompt engineering", which is forgivable.
[−] agent-kay 25d ago
[flagged]
[−] newsdeskx 25d ago
[flagged]