Ephemeral Boards (Coming soon)

Nyxen Ephemeral Boards are short-lived, encrypted work surfaces for structured collaboration that must not become a permanent knowledge base. Think of them as:

• a temporary situation room

• a shared notepad for one operation

• a tactical board that self-destructs

Not a wiki. Not a doc platform. Not a project tool. When the window closes, the board goes with it.

---

Concept

An Ephemeral Board is:

• Client-side encrypted

• Key-based (no account, no identity)

• Time-bound with a strict TTL

• Collaborative (multiple participants in real time)

• Non-persistent – burns completely at expiry or on command

Use cases:

• incident response notes

• negotiation points and updated terms

• “for call only” meeting notes

• temporary red-team / blue-team boards

• coordination in parallel with Dead Drops or Spectre Voice

[!IMPORTANT] Ephemeral Boards are designed to disappear. There is no archive or version history.

---

Core Properties

Property	Description
Access Model	Shared key or invite link (no login)
Encryption	Client-side (board content encrypted as structured payload)
TTL	Required at creation (e.g. 15–180 minutes)
Collaboration	Multi-user editing, no named identities
Storage	Ciphertext + TTL metadata only, purged on expiry/burn
Features	Minimal: sections, bullets, tasks, tags (no heavy formatting)

[!NOTE] Keep Board features intentionally narrow. The point is controlled expression, not document authoring.

---

Lifecycle

1. Create Board – define TTL and scope.

2. Share Access – send link/key.

3. Collaborate – edit live within the time window.

4. Expire / Burn – board is wiped.

5. No Recovery – nothing to “re-open” later.

---

1. Create

User opens Nyxen Boards and sets:

• TTL (e.g. 30, 60, 120 minutes)

• Optional label: IR-0924 bridge, Deal draft – call only, etc.

• Optional layout presets:

  • Notes

  • Tasks

  • Timeline

  • Key points

Nyxen client:

• generates boardId

• generates boardKey locally (never sent in plaintext)

---

2. Client-Side Encryption

Board content is encrypted as it changes.

Simplified model:

const key = await generateBoardKey();

function syncBoardUpdate(patch) {
  const { ciphertext, nonce } = encryptWithKey(key, JSON.stringify(patch));

  sendToNyxenRelay({
    boardId,
    nonce,
    ciphertext,
    expiresAt
  });
}

• Edits → encrypted patches

• Relay → only sees ciphertext + expiry

• Clients with key → reconstruct the board in memory

[!INFO] Real-time behavior (e.g. WebSocket) should operate exclusively on encrypted payloads.

---

3. Sharing Access

Same patterns as other Nyxen primitives.

Full link (simple):

https://nyxen.vip/board/B82Z1#Kf9sQ2...

Split key (recommended):

• Link:

https://nyxen.vip/board/B82Z1

• Key fragment over a separate channel.

[!TIP] Treat the board key as both view and edit access. Anyone with it is inside until TTL/burn.

---

4. Collaboration Rules

Inside an Ephemeral Board, participants can:

• add/edit bullet points

• mark quick statuses (e.g. [ ] / [x])

• maintain a short timeline

• track key decisions

No:

• comments with identity

• avatars or presence names

• document export

• integrations that mirror content elsewhere

Visual behavior:

• live updates

• visible TTL countdown

• clear “Ephemeral Board” warning state

---

5. Expiry & Burn

Board destruction follows Nyxen’s core rule set:

Automatic (TTL)

At expiresAt:

• All ciphertext associated with boardId is purged.

• New connections receive “Board expired”.

• Local clients wipe in-memory / cached content.

Manual Burn

Any authorized burner (configurable at creation) may:

• trigger Burn Board

• immediately invalidate the board

• instruct all connected clients to wipe and show burn notice

onBoardBurn(boardId) {
  clearBoardKey(boardId);
  clearBoardCache(boardId);
  renderBurnNotice("This Nyxen Board has been destroyed.");
}

[!WARNING] Burn is absolute. There is no hidden backup or “owner override”.

---

Recommended Usage Patterns

Scenario	TTL	Notes
Incident response scratch board	30–90 minutes	Pair with Dead Drop Room; burn post-incident.
Legal/negotiation talking points	30–120 minutes	For live calls only; final terms live elsewhere.
Temporary ops planning	30–60 minutes	Capture intent, not documentation.
Sensitive internal sync	15–45 minutes	Avoid turning into a de facto decision log.

[!TIP] If information from an Ephemeral Board must survive, manually move a redacted version into your own systems. Nyxen will not do it for you.

---

Example: Workflow

A practical example to include:

1. Create a Nyxen Dead Drop Room for live discussion.

2. Inside it, open a linked Ephemeral Board:

   • TTL: 60 minutes

   • Layout: “Key decisions + actions”

3. Participants:

   • Note only what’s needed to align.

   • Mark completed items during the call.

4. At the end:

   • If necessary, someone copies minimal outcomes into a secure internal system.

   • Hit Burn Board.

   • Dead Drop Room auto-expires at its own TTL.

Result: alignment and accountability without a permanent narrative living on a third-party platform.

---

Relationship to Other Nyxen Primitives

• Dead Drops – conversation.

• Secure Links – single message.

• File Drops – file hand-off.

• Ephemeral Boards – structured, shared context for a short window.

• Capsules – bundle all of the above for one operation.

All follow the same Nyxen doctrine:

Key-based. Client-side encrypted. Time-limited. Burnable. No archives.