decagondev

Module 2 Challenger — Take-Home

Representation & the Data/Code Seam: Choosing What Must Be Cheap · the first spectrum

Last time you named a binding constraint. The first thing that derivation hits is this: which operations have to be cheap? Answer that and you've chosen a representation — and a data structure is a bet. This take-home asks you to make that bet on a system you own, and then do the part everyone skips: name what you made expensive. The grade is in reading the whole ledger, not in picking a clever structure.

Time: ~45–60 min · Due: before Module 3 · Submit: post your write-up in the cohort channel.

---

decagondev

Module 1 Challenger — Take-Home

Constraint-First Design: Naming the Binding Constraint · the method

This is the first one, and it installs the move the whole course rests on. Before any architecture, you name the single constraint the design exists to relieve — then derive every decision from it. The grade is in the reasoning, not in finding a famous system: a clean derivation chain on a humble system beats a vague gesture at a clever one.

Time: ~45–60 min · Due: before Module 2 · Submit: post your write-up in the cohort channel.

---

decagondev

Hackathon Design Document — "Mid-Flight Engine Swap"

Fuses: CC5 (System Evolution) × CC2 (Incident & Resilience) × CC3 (Trustworthy Pipeline) Companion doc: cross-cutting-hackathons.md §10.3 Recommended slot: capstone — run last, once the brownfield harness and rubrics are proven.

Attribute	Value
Codename	Mid-Flight Engine Swap
Format	Brownfield migration + modernization, with a surprise drill and an adversarial review

decagondev

Hackathon Design Document — "The AI Wrote This"

Fuses: CC1 (Trust-but-Verify) × CC4 (Performance & Data-Shape) × CC5 (System Evolution) Companion doc: cross-cutting-hackathons.md §10.2 (and the §10 note on the 32K verification twist) Recommended slot: second flagship — run after the 32K rubric/harness is comfortable.

Attribute	Value
Codename	The AI Wrote This
Format	Brownfield break-fix + 32K-style design defense

decagondev

Hackathon Design Document — "Ship It or Sink It"

Fuses: CC2 (Incident & Resilience) × CC3 (Trustworthy Pipeline) Companion doc: cross-cutting-hackathons.md §10.1 Recommended slot: the first flagship blended event to run (per the sequencing in §12).

Attribute	Value
Codename	Ship It or Sink It
Format	Brownfield break-fix + pipeline hardening

decagondev

LinkedIn Applicant Qualification Pipeline — Systems Design

Status: Draft v1 for review Author: Drafted with Claude, from the Cohort 5 run + Slack operational log Scope: End-to-end pipeline from Firebase application data → profile data acquisition → triage → bucketing → outreach-ready output, plus the scaling, reliability, legal, and cost trade-offs.

---

0. TL;DR (read this first)

decagondev

LinkedIn Applicant Qualification — Costing Comparison

Scenario: Acquire and qualify 10,000 applicant LinkedIn profiles. Two paths compared: (A) a B2B enrichment API vs (B) the current Cowork + Claude-in-Chrome live-scrape pipeline. Pricing basis: public list prices and reported market figures gathered June 2026 (sources at the end). All figures are estimates to validate against live quotes; the ratio between the two paths is the durable finding, not the exact dollar amounts.

---

0. Bottom line

decagondev

title	Doppl — System Design & Concept Document
subtitle	An idea organism: markdown nodes under evolutionary selection
author	Synthesised from the Doppl contracts, the capstone proposal, and the doppl-prime/michael repo
status	Design reference (v1)
date	2026-06-23

Doppl — System Design & Concept Document

decagondev

Module 1 Challenger — Take-Home

Constraint-First Design: Naming the Binding Constraint · the method

This is the first one, and it installs the move the whole course rests on. Before any architecture, you name the single constraint the design exists to relieve — then derive every decision from it. The grade is in the reasoning, not in finding a famous system: a clean derivation chain on a humble system beats a vague gesture at a clever one.

Time: ~45–60 min · Due: before Module 2 · Submit: post your write-up in the cohort channel.

---

decagondev

Here is your optimized, generic prompt:

---

You are an expert Product Manager and Senior Software Engineer with deep experience in agile methodologies, software architecture, and technical documentation.

Your task is to create a complete foundational documentation suite for a new software project based on the user's input.

Required Deliverables

Generate the following professional markdown files with comprehensive, well-structured content: