01
Backend systems
API contracts, request authorization, concurrency and retry design.
Life / Backend / Security / Engineering notes
Programming, API design, reliability, security research, AI tooling, and the experiments that make complicated systems easier to inspect.
A space for the things I want to share
01
API contracts, request authorization, concurrency and retry design.
02
Trust boundaries, abuse cases, attacks, defenses, and tests.
03
Short reference implementations and reproducible educational labs.
Stories / Notes / Work in progress
No personal technology & security stories have been published in this collection yet. This section automatically fills with my own approved posts, notes, recipes, or build logs as I add them.
Visit the Life notebookPhotography / Original media
A spot for the first photograph
Original photos only, with descriptive captions
Stories behind the images
Details and context, not stock or invented travel photos
Photo entries appear automatically after original pictures and captions are approved and added to the Life notebook.
Engineering / Inspectable examples
Small educational examples, not customer code or claims of deployed robotics, firmware, or backend systems. Open any sample for its checks, source references, and limitations.
TypeScript / Tested teaching helper
interface Decision { authenticated: boolean; authorized: boolean; integrityOk: boolean }
export function canMutateResource(input: Decision): boolean {
return input.authenticated && input.authorized && input.integrityOk;
}A client or attestation verdict cannot grant access to someone else's object.
SQL / Reference example
CREATE TABLE operation_requests (
tenant_id text NOT NULL,
operation_key text NOT NULL,
request_fingerprint text NOT NULL,
status text NOT NULL,
response_json jsonb,
created_at timestamptz NOT NULL DEFAULT now(),
PRIMARY KEY (tenant_id, operation_key)
);A uniqueness constraint is the foundation for atomic operation claims.
TypeScript / Tested teaching helper
export function authEvent(input: {
operation: string; outcome: 'allowed' | 'denied';
token?: string; password?: string;
}) {
return {
event: 'auth.decision',
operation: input.operation,
outcome: input.outcome
};
}Create a structured outcome without recording the input's token or password.
Already on the site / Related material