Projects | Sunny Patneedi

Current work

Two cases: my role, one decision, the evidence, and its limits.

Browse the archive

Puddle

Experiment

Checked 9 October 2026

Does a parent need another feed, or one small next step?

Audience: Parents
My role: Solo builder.
Decision: A playbook of options the parent chooses. Not an open chat that answers for them.
Evidence: The public page at askpuddle.com loaded on 9 October 2026.
Limits: I did not check the onboarding flow. The page does not show that the guidance helps a family. Puddle makes no medical, developmental, or compliance claims.
Open question: Which suggestions do parents try or adapt? The onboarding flow needs a dated check before any Available label.

Visit askpuddle.com

SPEAR

Experiment

Checked 9 October 2026

How can an AI application's security behavior be inspected, not just asserted?

Audience: Engineers building LLM applications
My role: Builder of the open-source middleware.
Decision: Put checks at the runtime boundary and publish an evaluation harness. Do not treat provider safety filters as the whole boundary.
Evidence: The public repository shows the source tree, README, and evaluation method.
Limits: Source access is not a released package or hosted service. The checks cover input screening and deterministic agent controls. They do not cover live-model output leakage or production latency.
Open question: What changes with live models, new attacks, and real integrations? A bounded evaluation does not guarantee complete protection.

View source

The project archive

Current work and earlier experiments. A link appears only where I verified a public destination. Entries without a dated check are unverified and carry no link.

Status legend

Available:: The intended public flow was checked at its exact destination.
Private preview:: Access is limited.
Experiment:: Prototype or exploratory work. Not a promise that it is ready to use.
Planned:: Intent only.