From 6939d6678f18aaf08b419bc5356cb0cfbfb47b46 Mon Sep 17 00:00:00 2001 From: Louis Beaumont Date: Fri, 2 Oct 2026 10:54:57 -0700 Subject: [PATCH] Align Paris tracks with Luma and add participant preparation checklist --- README.md | 13 ++++++++++++- docs/get-ready.md | 33 +++++++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+), 1 deletion(-) create mode 100644 docs/get-ready.md diff --git a/README.md b/README.md index 6be02c8..3835fa8 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,6 @@ + # Build agents that remember how work gets done Watch someone do a real task, document it accurately, and help someone else repeat it. Nine projects for the [42 Paris hackathon, October 16 to 18](https://luma.com/bnre6nou). @@ -89,12 +90,22 @@ Only `--ai` sends the selected records to that provider, which may charge separa Use fictional or permissioned data for invoice investigation, order exceptions, onboarding handoffs, support escalation or another repeated task. [Project ideas and acceptance tests](ideas.md). -The event tracks remain **Agents That Remember**, **Your Data, Your Interface**, and **Wildcard**. These starters give the tracks a concrete starting point. They do not change the organizer's rules or judging criteria. +The [event page](https://luma.com/bnre6nou) lists these tracks (checked October 2, 2026): + +| Track | Starting points in this repo | +|---|---| +| **Find what to automate** | [Repeated-task finder](examples/repetition-finder/README.md), [evidence search](examples/evidence-search/README.md), [work session to SOP](examples/work-session-sop/README.md) | +| **Teach an agent your workflow** | [Workflow review desk](examples/workflow-review/README.md), [reviewed workflow to replay](examples/workflow-replay/README.md) | +| **Make it work for a team** | [Shift handoff](examples/shift-handoff/README.md), [onboarding walkthrough](examples/onboarding-walkthrough/README.md), [SOP change review](examples/sop-change-review/README.md), [support escalation packet](examples/support-escalation/README.md) | + +These are suggested starting points. The organizers' event page is the source for current tracks and rules; the projects do not add judging requirements. Optional smaller examples are still available: [meeting follow-up](examples/meeting-followup/README.md) and the [work-memory browser](examples/work-dashboard/README.md) at `/memory`. ## Participant resources +Before the weekend, [follow the preparation checklist](docs/get-ready.md) to arrange access, install Screenpipe, try the sample data and find help. + - [Event registration and organizer Discord details](https://luma.com/bnre6nou). Follow the organizer's `#hackathon-access` instructions. - Participant Business access: the 30-day page is being prepared. Organizers will share it after activation is verified. The samples already work without a subscription. - [Install Screenpipe](https://screenpipe.com/download), [local API setup](docs/local-data.md), [submission checklist](docs/submission.md). diff --git a/docs/get-ready.md b/docs/get-ready.md new file mode 100644 index 0000000..2f5cdaf --- /dev/null +++ b/docs/get-ready.md @@ -0,0 +1,33 @@ + + + +# Get ready for the hackathon + +Build Agents That Remember takes place October 16 to 18 at 42 Paris. [Register and check the event details on Luma](https://luma.com/bnre6nou). + +## 1. Arrange participant access + +The 30-day Screenpipe Business offer is being prepared. Organizers will share the participant page once activation is verified. Access runs from the day you claim, with no credit card or automatic paid renewal. If you already have access, keep using it and contact the organizers if needed. External AI providers may charge separately. + +## 2. Install and try a small capture + +[Download Screenpipe](https://screenpipe.com/download), sign in with the account you used to claim access, and follow the app's permission prompts. Try it before the weekend so you have useful work history to build with. Record a small task you are comfortable using, then check that you can find it in the app. See [local data setup](local-data.md) for the API connection and troubleshooting. + +## 3. Run the fictional sample + +You can start immediately without Screenpipe history, a subscription or an AI key. Install [Bun](https://bun.sh/docs/installation) 1.3 or newer, then: + +```sh +git clone https://github.com/screenpipe/hackathon-starter.git +cd hackathon-starter +bun run demo +bun start +``` + +Open http://localhost:4242 to review the sample workflow. Return to the [nine projects and track suggestions](../README.md#choose-a-useful-problem) to choose your starting point. + +## 4. Join the community and prepare your demo + +Use the Discord invitation in your organizer email and follow the `#hackathon-access` instructions to get the participant role. Ask the organizers for help if you cannot find the invitation. [Luma](https://luma.com/bnre6nou) has the host contact and current event details. + +Use the [submission checklist](submission.md) to prepare your project. The organizers will confirm the final destination and deadline.