• Write a program that opens a TCP socket and listens on a port
• Send a request to it — from your browser or with curl localhost:port
• Print the raw output
• That text you see? That's HTTP. That's all it ever was.

Now parse that raw text. Pull out the method (GET, POST), the path (/about, /api/users), the headers. Write the parser yourself, split on newlines. Handle the edge cases.

Done when: your code can tell you what path, method any request is asking for.

When someone asks for /about, your server needs to know what to do. Build that system. Design your API — what should using YOUR framework feel like? This is your creative decision. This is why no two Draco frameworks look the same.

Done when: different paths call different functions.

After your router works, your handlers need to send something back to the browser. Write a function that puts a response onto the socket — status code, headers, body — and wrap it into something clean like res.send() or res.json(). Your design, your call.

Now your framework can receive a request, route it, and reply to it. That's it. That's a working framework. Give it a name, publish it to npm, build a real web-app, and write its backend using your own framework, deploy it live, and send us the link!