tegwick
f6e7a03afb
State the parking-lot intent, the nudges/ convention, and the concept for a later Forgejo-backed topic heatmap. Register the bootstrap workplan. Assistant: grok Assistant-Session: 01a107f5-2e61-7df1-ab4e-f9cb9fe2199c
3.8 KiB
| domain | repo | updated |
|---|---|---|
| infotech | nudge-space | 2026-10-04 |
INTENT
This file explains why nudge-space exists, what role it plays in the ecosystem, and what it must not absorb.
Why it exists
Participants in this ecosystem keep noticing things that are relevant, and that are not ready to become work. Turning each one into a task would spend the focus the work needs. Dropping each one would throw away a signal that might matter later, or that might show up again and again.
Nudge Space is the parking space for those notices. In an agile meeting the parking lot holds a thought that has relevance and does not have the floor. Here the same thought is written down, left in peripheral view, and kept available for when it is needed or when it recurs.
The repository is a semi-structured collection at the very beginning of value and product discovery. A nudge is earlier than an intake. It is a hunch with an origin, not a commitment.
The governing principle
nudge-space owns peripheral attention.
It should answer:
- What have people noticed? Hunches, unfinished ideas, and recurring themes, each with a pointer back to where they were encountered.
- Where does attention gather? A topic heatmap, in the spirit of a word cloud, that develops as nudges accumulate.
- What is still only a hunch? The record stays a nudge until someone deliberately promotes its substance into a work record somewhere else.
A nudge stays in the periphery. Elaborating it here, or filing it as a task so it will not be forgotten, spends the focus this place exists to protect.
What it is
nudge-space is the discovery periphery for the ecosystem.
It contains:
- the intent and concept for that periphery
- the convention by which a repository connects: a
nudges/folder of semi-structured notes - later, a read of those folders through Forgejo, and a search and exploration space over what they contain
The source of a nudge stays in the repository where it was encountered. This repository collects and, in time, projects. Participants keep editing their notes at home.
What it is not
| Concern | Where it belongs |
|---|---|
| Executable work, acceptance, owners, deadlines | A workplan in the owning repository |
| A spark someone has decided should enter coordination | An intake in the owning repository |
| Decisions, canon, and standards | The owning repository, or the-custodian |
| Product design and implementation of an idea | The repository that takes the idea up |
| A ranked backlog | Nowhere. Recurrence is a signal, and a signal is not an assignment |
Promotion is a separate act. Someone copies the substance into a work record in the repository that should own it, and may leave a pointer on the nudge. The nudge file remains.
What it enables
When this repository is doing its job, a participant can:
- park a hunch in the repository where it appeared, under
nudges/, and go back to the work - find that hunch again, with its origin
- see which themes recur across repositories, as a heatmap that develops over time
- choose, in a later sitting, whether a recurring theme deserves to become real work
Design values
Focus stays with the work. Recording a nudge is a small act. Refining it waits for a deliberate promotion.
Origin stays attached. A nudge names where it was encountered.
The source stays put. Participant repositories keep their own nudges/
folders. Nudge Space reads them through Forgejo.
Recurrence is the interesting event. A theme that returns, across days or across repositories, is the signal worth seeing. A single hunch can sit quietly.
Rough on purpose. The collection is semi-structured. Enough shape to search and to cluster. Little enough shape that it cannot become a second task system.