# Project Profile

- Project Name: Nightnibble
- Preferred X Username: @nightnibble
- X Bio: Small tasks. Long nights. Compare AI task estimates, set a budget, and save tomorrow's queue. A local planning desk for developers.
- Token Name: Nightnibble Credits
- Token Ticker: NIBL
- Token Description: Nightnibble helps developers compare local AI task budgets and save queues. A proposed 1% buy/sell creator tax would allocate its revenue: 60% to developer inference grants against verified task receipts, 25% to product development, and 15% to operations. Distribution would require manual review.

## Pre-launch Tweet 1

```text
One screen wakes. Then another.

Nightnibble is clocking in: a midnight desk for the tasks that keep eating your AI budget.

Small tasks. Long nights.
```

![A single CRT wakes the dark Nightnibble server aisle](pre-launch-1.png)

## Pre-launch Tweet 2

```text
Before the big request, try a small calculation.

Pick a task. Set an input/output budget. Compare estimates before saving a local queue.

Nightnibble gives the night shift a planning desk.
```

![Task cards and an amber budget dial on a midnight workbench](pre-launch-2.png)

## Project Launch Tweet

Publish after the canonical website has been verified reachable.

```text
Meet Nightnibble. Compare AI task estimates, cap a budget, and save a local queue.

Explore the local demo:
https://www.nightnibble.xyz/

Proposed, unissued: Nightnibble Credits
$<ticker>
CA: <ca>
```

![The Nightnibble local demo control desk](project-launch.png)

## Follow-up Tweet 1

```text
Spark, Forge, or Deepwork?

These are editable fictional model profiles. Change their rates and see how your estimate moves.

Which profile would you tune for your next task?
```

![Three editable model profile terminals](follow-up-1.png)

## Follow-up Tweet 2

```text
A short prompt can ask for a very long answer.

Nightnibble separates input and output tokens in the estimate. Change one side, then the other.

Which side takes the bigger bite in your task?
```

![Separate cyan input and amber output conduits](follow-up-2.png)

## Follow-up Tweet 3

```text
The amber line has a job.

Try adding a task that pushes your local queue past its budget cap. Then adjust the task or the cap and try again.

What limit would make your next experiment comfortable?
```

![An amber budget gate stops a cyan task card](follow-up-3.png)

## Follow-up Tweet 4

```text
Leave tomorrow a tidy queue.

Save a few tasks in Nightnibble, reload the page, and find them in this browser's local storage.

What is the first task you would leave for your next shift?
```

![Task cards preserved in a local archive drawer](follow-up-4.png)

## Follow-up Tweet 5

```text
What if credits changed the estimate?

Turn the hypothetical discount and compare the result. It is an assumption you control, not an available supply offer.

Which discount would change how you plan a task?
```

![A hypothetical credit discount dial](follow-up-5.png)

## Follow-up Tweet 6

```text
Pack the plan before you leave.

Export your Nightnibble queue manifest and inspect the tasks and estimates outside the desk. Exporting does not run a model.

What would you add to your planning manifest?
```

![A local queue manifest emerges from a midnight printer](follow-up-6.png)

## Follow-up Tweet 7

```text
The night shift has an empty chair.

Try the budget planner, then tell us what felt unclear: model rates, token counts, credit assumptions, or the queue?

One specific example is worth a whole server room of vibes.
```

![An empty chair invites feedback at the Nightnibble terminal](follow-up-7.png)
