The toy JSON example keeps its boundary narrow.

highlighted = computed this step

What this toy model checks

The trust boundary parses one POST request, checks its JSON Content-Type and length, then accepts one pinned JSON object.

recompute JSON rows\text{recompute JSON rows}
JSON honesty boundaryThe body bytes, parsed JSON fields, and length check are recomputed from pinned POST bytes.JSON honesty boundary - POST /api JSON body 17 bytes, fields ok=true and n=3sectionnamevaluecheckrequest linemethodPOSTparsedrequest linepath/apiparsedrequest lineversionHTTP/1.1parsedheaderHostapi.exampleexactheaderContent-Typeapplication/jsonJSONheaderContent-Length17declared bytesbodydisplay wordsok true comma n threesafe display formbodyexact hex7b226f6b223a747275652c226e223a337dpinned bytesbodybyte length17countedfieldokok=trueparsedfieldnn=3parsedcheckContent-Length17declaredcheckbody bytes17recomputedcheckmatchyessame count

Honesty boundary

NOTE: toy HTTP JSON body only; not full JSON edge cases, Unicode or escaping beyond pinned ASCII, schema validation, arrays or nested objects, streaming, chunked transfer, compression, auth, CORS, frameworks, API versioning, or production server config.

toy JSON body only\text{toy JSON body only}
JSON honesty boundaryThe body bytes, parsed JSON fields, and length check are recomputed from pinned POST bytes.JSON honesty boundary - POST /api JSON body 17 bytes, fields ok=true and n=3sectionnamevaluecheckrequest linemethodPOSTparsedrequest linepath/apiparsedrequest lineversionHTTP/1.1parsedheaderHostapi.exampleexactheaderContent-Typeapplication/jsonJSONheaderContent-Length17declared bytesbodydisplay wordsok true comma n threesafe display formbodyexact hex7b226f6b223a747275652c226e223a337dpinned bytesbodybyte length17countedfieldokok=trueparsedfieldnn=3parsedcheckContent-Length17declaredcheckbody bytes17recomputedcheckmatchyessame count

No client compute

The page shows already validated rows. It does not parse JSON in browser code.

static validated rows\text{static validated rows}
JSON honesty boundaryThe body bytes, parsed JSON fields, and length check are recomputed from pinned POST bytes.JSON honesty boundary - POST /api JSON body 17 bytes, fields ok=true and n=3sectionnamevaluecheckrequest linemethodPOSTparsedrequest linepath/apiparsedrequest lineversionHTTP/1.1parsedheaderHostapi.exampleexactheaderContent-Typeapplication/jsonJSONheaderContent-Length17declared bytesbodydisplay wordsok true comma n threesafe display formbodyexact hex7b226f6b223a747275652c226e223a337dpinned bytesbodybyte length17countedfieldokok=trueparsedfieldnn=3parsedcheckContent-Length17declaredcheckbody bytes17recomputedcheckmatchyessame count

Summary

A JSON body can carry named fields after the headers.

JSON names fields\text{JSON names fields}
JSON honesty boundaryThe body bytes, parsed JSON fields, and length check are recomputed from pinned POST bytes.JSON honesty boundary - POST /api JSON body 17 bytes, fields ok=true and n=3sectionnamevaluecheckrequest linemethodPOSTparsedrequest linepath/apiparsedrequest lineversionHTTP/1.1parsedheaderHostapi.exampleexactheaderContent-Typeapplication/jsonJSONheaderContent-Length17declared bytesbodydisplay wordsok true comma n threesafe display formbodyexact hex7b226f6b223a747275652c226e223a337dpinned bytesbodybyte length17countedfieldokok=trueparsedfieldnn=3parsedcheckContent-Length17declaredcheckbody bytes17recomputedcheckmatchyessame count