← Back to Demand Signal Radar
PUBLIC VALIDATION BRIEF

[BUG] Native gemini provider: 400 "Unknown name additionalProperties" in tool schemas (regression vs 0.3.1)

Evidence observed in afjcjsbx/picoclaw, a Productivity project.

8 comments0 positive reactions25 days openProject Radar 80
bug
Start the no-account validation tool4 guided steps · private browser notes · export anytime
DEMAND CONFIDENCE

REPEATED ACROSS 11 PROJECTS

Related friction appears in 11 independent repositories. This is stronger than one backlog item, but still requires direct user validation.

Project strength and demand confidence are measured separately.
SOURCE EVIDENCE

Start with what users actually said

Reporter context: Quick Summary With the native provider, every request fails with HTTP 400 "Unknown name "additionalProperties"" in the tool definitions. The same setup worked on sipeed v0.3.1, so this looks like a regression in tool-schema sanitization for the native Gemini API. Environment & Tools PicoClaw Version: v0.5.2 (git…Excerpted from the public Issue. Read the complete thread before interpreting it.

Read original GitHub Issue ↗
PRODUCTIVITY VALIDATION LENS

Recruit: Recruit people who repeat the task every week and can show their current calendar, notes or coordination workaround.

Guardrail: Measure repeated use and time returned across two cycles, not a one-time demo completion.

01 · Provider interoperability

Write the problem hypothesis

For [team], moving data between [system A] and [system B] requires [manual work], causing [delay or errors].

You can name one user, one situation and one measurable consequence without proposing a feature.
02 · EVIDENCE INTERVIEW

Interview five operators or knowledge workers

  • Which systems must exchange data?
  • What triggers the handoff?
  • Which fields or permissions block it?
  • How is it handled today?
  • Who owns failures between systems?
At least three people independently describe the same painful workflow with recent examples.
03 · MINIMUM TEST

Run the smallest experiment

Manually operate or prototype one high-frequency connection for one team before building a general connector.

A user completes the real cross-system workflow twice and asks to keep the connection active.Measure repeated use and time returned across two cycles, not a one-time demo completion.
04 · DECISION GATE

Make a build decision

  • Build: repeated pain and active commitment
  • Narrow: pain is real but the audience or job differs
  • Stop: weak frequency or no behavioral proof
Do not let GitHub engagement replace direct validation.

Why this brief exists

Information has value only when it changes action. This page turns one public signal into a bounded validation exercise. It is a research aid, not proof of demand, investment advice or a product recommendation.