LYNFOLD Core MarkLYNFOLD繁中

PRODUCT FOUNDATION

A personal context layer for AI, under your control

LYNFOLD keeps the context around AI work in a process you can understand, inspect, and control.

01 / Product

Carry your personal context into the work at hand.

LYNFOLD is a personal context governance layer for AI, under your control. It keeps important information in a process you can understand and inspect, so a new AI conversation can pick up where you left off.

01STARTAI conversation
02ORGANIZELYNFOLD
03CONFIRMGovern
04CHOOSERetrieve
05CONTINUEResume with AI

02 / What LYNFOLD keeps

Keep what you will need later as context you can understand.

LYNFOLD keeps important background, progress, decisions, and relationships across six Core Entity types. Structured information can then be found, checked, and carried forward.

  1. 01

    Information

    Concrete information worth keeping and finding again.

  2. 02

    Project

    Work in progress and the context around it.

  3. 03

    Decision

    Choices that have been made and still matter.

  4. 04

    Event

    Something that happened with time and context.

  5. 05

    Person

    A person connected to the work or context.

  6. 06

    Organization

    A group or institution connected to the context.

03 / When information changes

Keep the past, make the present clear.

What was true before may not be what should be used now. LYNFOLD separates current data, past records, conflicts, and provenance so change stays visible.

  1. 01

    Current State

    Current data

    Information that should be prioritized for ordinary search and the next AI conversation.

  2. 02

    History

    Change history

    Information used or recorded before, without mixing it with the current version.

  3. 03

    Conflict

    Needs confirmation

    When two values conflict, keep the conflict visible instead of overwriting one silently.

  4. 04

    Provenance

    Source context

    Keep where information came from and how it changed, so a decision has evidence.

04 / AI Import

AI proposes. You confirm. LYNFOLD persists.

AI can help organize candidate information, but importing is not writing a block of text directly into the database. Candidates pass through parsing, validation, identity resolution, evolution comparison, and preview first.

  1. 01

    AI proposes

    AI produces possible important information and source details.

  2. 02

    Preview

    LYNFOLD parses and validates the input, resolves identity, and explains the operations it proposes.

  3. 03

    You confirm

    Review candidates, conflicts, and changes before selecting the Commit Plan.

  4. 04

    Trusted persistence

    Only confirmed data is persisted; the confirmed Commit Plan succeeds completely or rolls back.

AI input is data, not executable authority. LYNFOLD does not let AI create authoritative data directly or make the final governance decision for you.

05 / Identity

Names can change. Identity stays stable.

A name describes an Entity; it does not define the Entity. LYNFOLD resolves whether something is the same Entity before it handles a data change.

  1. 01

    Stable Entity ID

    A stable ID defines persistence identity, even when a name changes.

  2. 02

    Canonical Name

    The primary name currently used to describe an Entity.

  3. 03

    Active Alias

    A still-valid previous name or alias; Alias is distinct from Tag.

  4. 04

    Identity before evolution

    Resolve the Entity first, then decide whether data is new, updated, corrected, or in conflict.

Different Entity Types are not merged. Full Existing Entity Merge is Post-Beta; similar names do not trigger automatic merging.

06 / Search and Retrieval

Find what matters, then know what to use now.

Local Search helps you find the context kept on your machine. Retrieval then selects what is actually relevant to the work in front of you.

01

Local Search

Start with local data

Search Canonical Names and Active Aliases across the six Core Entity types.

02

Current-first Retrieval

Use the present first

Confirmed Current State is the default priority; History is not mixed into current data.

03

Minimum sufficient context

Do not dump everything into AI

Finding information does not mean carrying all of it forward; choose what this task actually needs.

07 / Resume with AI

Select → Preview → Copy → Paste

Select a starting point and a goal, inspect the exact context you are about to give AI, then use Copy/Paste to carry the work into the next AI conversation.

  1. 01

    Select

    Choose a starting Entity and what you are working on now.

  2. 02

    Preview

    Inspect the exact outgoing context; Current comes first, History is off by default, and unresolved Conflicts are marked clearly.

  3. 03

    Copy

    Copy the material for AI; an actual Copy saves an audit snapshot of what was sent.

  4. 04

    Paste

    Paste it into the next AI conversation and continue across sessions or providers.

Copy/Paste is the formal Internal Beta transport. This workflow does not require a paid AI API and does not claim Direct AI integration.

08 / Backup and Ownership

You own the data. You control the backup.

Local-first keeps the core data centered on your machine. Full Backup and Restore provide a checkable path for data safety and recovery.

01

Local-first

Core data storage and governance are currently centered on the local workspace.

02

Full Backup

Create a complete backup without changing Current data.

03

Restore = Replace

Create a safety backup first; after validation, Restore replaces the live data as a whole. It does not merge.

LYNFOLD makes your context understandable, reviewable, and portable; it does not hand the final control of important data to AI.

09 / Current Status

We separate where the product stands today.

What is validated, what is waiting for evidence, and what we do not claim complete are kept distinct.

  1. 01

    v1.2.1 current test build

    The current validated test build.

    Owner Validation complete
  2. 02

    Trusted Tester validation

    External tester evidence is still pending.

    Not started
  3. 03

    Internal Beta

    Overall Beta completion is not claimed.

    Completion not claimed

10 / Current Boundaries

Know what is here now—and what is not.

These are the boundaries the current product and public story follow. Anything not listed as a current capability is not presented as a completed product promise.

Current product focus

  • Local-first
  • 6 Core Entity types
  • Current / History / Conflict / Provenance
  • AI Import with preview and user confirmation
  • Local Search
  • Resume with AI through Copy/Paste

Not claimed or not in the current build

  • Cloud Sync
  • Accounts
  • Mobile
  • Direct AI integration
  • Vector Search
  • Automatic duplicate merge
  • Market validation