Guide

Usage Guide

Personal knowledge design notes before the public Norfolk launch opens.

Use Case

Throw It In. Watch It Connect.

📥

1. Dump Everything Into Inbox

Don't organize. Don't think. Just throw it in.

• "venue costs went up 15%"

• "curator confirmed for opening night"

• "need to order 50 chairs by Friday"

• "budget meeting notes - Q4 projection"

• "artist wants spotlight on installation"

• "floor plan v2 attached"

Voice memos. Screenshots. PDFs. Random thoughts at 2am.
Everything lands in the same place.

2. Drop One Purpose Anchor: "Exhibition Planning Meeting"

That's it. Norfolk does the rest.

→ Create Anchor: "Exhibition Planning Meeting"

One anchor. All related fragments gravitate toward it automatically.

📄

3. Open the Result — Already Reconstructed

Norfolk reconstructs the current thinking from scattered fragments.

Exhibition Planning Meeting — Summary

Budget: Venue costs +15%. Q4 projection reviewed. Chair order pending.

Confirmed: Curator for opening night. Artist requests spotlight on installation.

Action Items: Finalize chair order. Review floor plan v2. Confirm spotlight setup.

Not a blank page. A found page. Your scattered thoughts, assembled.

Stop organizing. Start throwing things in.

Norfolk connects the dots you didn't even know existed.

Check launch status

Workflow

How Norfolk Works

01

Knowledge Inbox

Collect notes, files, links in one place. This is your raw knowledge intake layer.

02

Atomize & Structure

Break captured input into atomic knowledge units. Fragments become reusable knowledge.

03

Anchoring

Create purpose-centered context. Anchors connect related knowledge under one working theme.

04

Knowledge Base

Keep your knowledge state fresh via search and reconstruction, then share results with team or project.

Next Step

Review launch status, planned plan boundaries, and the workflow before public Norfolk access opens.