curiositech
@curiositech Organization
Public Skills
agent-identity-continuity-reputation
by curiositech
Design durable agent identity and reputation systems for multi-agent / coding-agent fleets. Use when building or reviewing: agent memory/checkpoint that survives a process death, "persons not spawns" (role + continuity), registered outcome ledgers, Elo/Bradley-Terry/TrueSkill reputation for backends or agents, learned-outcome (bandit) routing, and agentic LLM-as-judge reviews. Covers the chain memory+checkpoint -> continuity -> durable person -> registered outcomes -> reputation -> a tradeable/hireable asset, and the failure modes that make each link theater (Sybil-reset, whitewashing, Goodhart, judge bias, cold start). Triggers: "agent reputation", "Elo for backends/agents", "agent identity that survives respawn", "outcome ledger", "learned routing", "resurrection with teeth", "episodic memory for agents", "credit assignment for agents".
context-economics-for-agent-swarms
by curiositech
Treat tokens as a coding swarm's cost-of-goods-sold AND its legibility engine. Covers per-agent context budgeting, compaction strategies (in-context summarization, structured note-taking, sub-agent isolation), the shared digest as compaction-for-humans- and-agents, the context-degradation cascade (lost-in-the-middle, context rot, recursive- summarization collapse), and mechanism design for metering token spend across a fleet. Activate on: "token budget", "context budget per agent", "compaction strategy", "digest / briefing as compression", "context window degradation / context rot", "summarization collapse", "COGS for agents", "metering agent token spend", "pheromone decay as forgetting", "/context-economics-for-agent-swarms". NOT for: memory storage architecture (use always-on-agent-architecture), single-prompt wording (use prompt-engineer), pure mechanism-design proofs (use nisan-et-al-2007-algorithmic-game-theory).
cdm-interviewer
by curiositech
Conduct Critical Decision Method (CDM) interviews to elicit expert reasoning strategies (L3 knowledge) from practitioners about specific challenging past incidents. Use when capturing expertise for skill development, preserving knowledge before practitioner departure, building post-incident learning artifacts, or investigating decisions in complex sociotechnical systems. Outputs structured incident reconstructions with cues, decisions, alternatives considered, and counterfactual analysis suitable for distillation into skills or training material.
closed-form-marbling-renderer
by curiositech
Render mathematically-faithful Turkish marbling (Ebru) and paper-marbling with closed-form coordinate-deformation maps — a drop is a radial outward push, a comb/tine is a decaying shear, all composed as homeomorphisms over colored region boundaries. No fluid solver, runs 60fps on a 2D canvas. Use when building a marbling/Ebru toy or generative-art renderer, implementing drop/comb/wave/swirl deformations, scripting traditional patterns (Battal, Gel-Git, Şal, Bülbül Yuvası), keeping combed edges crisp via adaptive resampling, modeling ox-gall shouldering for crisp ring-in-ring drops, or exporting high-DPI marbled prints. NOT for real fluid / Navier-Stokes simulation, metaball / alpha-blended "smoke" blob effects, raster image-processing filters, or non-marbling generative art.
agent-discovery-directories-guilds
by curiositech
Design discovery, directories, and guilds for agent swarms at scale. Use when many agents (5 -> hundreds) must FIND each other on a shared surface: capability indices, yellow-pages directories, whois/phonebook routing, reputation-aware discovery, and guild structures that scope trust. Covers the canonical prior art (FIPA Directory Facilitator, Contract Net, Chord/DHT, DNS-SD/Consul, EigenTrust, Greif's merchant guilds) and the failure modes (read-poverty, Sybil reset, Goodhart on rank, directory staleness, cold-start). Triggers: "agents can't find each other", "who owns this file/skill", "route a question to the right agent", "capability registry", "agent reputation", "guild / federation of fleets".
agent-creator
by curiositech
Design and scaffold new skills, subagents, and MCP surfaces. Use when choosing which primitive to create. NOT for invoking existing agents, generic coding help, or deployment work.
beale-rise-up-revolt
by curiositech
Russell Beale's "Rise up, Revolt!" analysis of why users blame themselves for bad design, and how consciousness-raising (not designer education) is the lever that fixes usability at a market level
alphago-deep-rl
by curiositech
Apply AlphaGo-style patterns: learned priors plus search, mixed evaluators, self-play, and asynchronous fast/slow loops. Use for intractable search and compute allocation. NOT for basic supervised learning, tractable optimization, or domains without search bottlenecks.
bordini-hubner-2007-jason
by curiositech
Jason multi-agent platform implementing AgentSpeak(L) for practical BDI agent programming and deployment
agha-actor-model
by curiositech
Foundational concurrent computation model where actors communicate exclusively through asynchronous message passing
bdi-soft-systems
by curiositech
Integration of BDI agent architecture with soft systems methodology for complex organizational problem-solving
agentspeak-bdi
by curiositech
Apply AgentSpeak(L) BDI architecture to event-driven autonomous agents with persistent goals, context-sensitive plans, and explicit selection functions. Use when designing interrupts, scheduling policies, or multi-agent coordination without a central controller. NOT for purely reactive rule systems, static planners, or ordinary ETL-style pipelines.
bratman-israel-pollack-1988-plans-resource-bounded-reasoning
by curiositech
Use for bounded reasoning, partial planning, commitment policy, deliberation cost, and reconsideration-threshold design instead of assuming free deliberation. NOT for exhaustive planning, static optimization, or domains where reconsideration cost is irrelevant.
bdi-agency-model
by curiositech
BDI (Beliefs-Desires-Intentions) agency framework for designing autonomous agents with mental state architectures
bdi-models-and-systems-reducing-the-gap
by curiositech
Implement executable BDI reasoning with explicit negation, paraconsistent revision, trigger-based commitment updates, and abduction. Use for runtime agent semantics and conflicting desires. NOT for purely axiomatic modal logic, black-box planners, or classical logic without operational semantics.
cryptoeconomic-protocol-security
by curiositech
Analyze bonded agent systems, escrow workflows, slashing rules, oracle trust, Sybil cost, and front-running risk in protocols where agents post bonds or stake reputation. Use for collateral sizing, griefing analysis, dispute design, and bonded-agent security reviews. NOT for smart contract auditing, DeFi tokenomics, blockchain consensus design, or trading strategy.
bdi-agent-design-mora
by curiositech
Design patterns for BDI agents using the MORA methodology for practical multi-agent system development
bellifemine-2007-jade-fipa
by curiositech
JADE platform for building FIPA-compliant multi-agent systems with standardized agent communication
api-versioning-strategy
by curiositech
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs. NOT for GraphQL schema evolution, gRPC/Protobuf wire compatibility, database schema migrations, or library/SDK semver.
content-security-policy-headers
by curiositech
'Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.'
circuit-breakers-and-retries
by curiositech
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book. NOT for server-side rate limiting, bulkhead isolation, backpressure protocols, or database-specific retry.
cdn-cache-control-headers
by curiositech
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — Cache-Control directives per RFC 9111, stale-while-revalidate and stale-if-error per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs. NOT for service-worker or browser-only caching, Redis/memcached application caching, or edge-function compute.
background-job-queue-design
by curiositech
'Use when designing a background-job system, choosing between BullMQ / Sidekiq / RQ / Temporal / SQS, deciding queue-vs-workflow, sizing concurrency vs rate limits, building dead-letter queues, or making handlers idempotent. Triggers: jobs running twice on retry, lost jobs after worker crash, DLQ filling up, Redis OOM from job backlog, exactly-once requested, "do we need Temporal?", visibility timeout / lockDuration confusion, exponential backoff vs jitter, fan-out fan-in workflows. NOT for outbound webhook publishing (different concerns), receiver-side webhook handling (different concerns), event-streaming/Kafka topology, or in-process async (event loop only).'
agent-compliance-conformance
by curiositech
Audit a compliance-ladder design (C0-C6) and transcript-fidelity ladder (T0-T5) plus their adapter conformance fixtures — Codex, Claude Code, Cloudflare, Ollama/LM Studio, custom stdio/HTTP agents — for the two failure modes that make a C-badge or T-fidelity label a lie: the ladder disagreeing with itself across doc/schema/ui/probe surfaces, and a level being reachable by self-report because no daemon-witnessed negative probe actually tries to forge it. Use when designing or freezing a compliance ladder, wiring an adapter conformance probe suite, deciding whether a numeric C-badge or T-label is safe to ship, or investigating a self-attestation or observed-to-controlled bypass risk. NOT for auditing a cryptographic protocol or whitepaper for adversarial soundness (redteam-review), writing TLA+/formal invariants for a daemon monitor (runtime-verification-for-agents), or agent identity, successor linkage, and reputation across restarts (agent-identity-continuity-reputation).