Published a Developer Notes Archive Recording 5BY.AI's Philosophy and Design Decisions

We added a developer notes archive explaining 5BY.AI's identity, memory design, user control principles, and long-term direction that are hard to convey through product features alone.

5BY.AI is hard to explain by its AI conversation saving feature alone. The core of the product lies in design decisions: why it reduces automatic judgment, why it values exploration and reentry over search, and how it distinguishes Pack from Anchor. To publicly record this background, we added the /notes archive.

Features are visible on screen, but why those features were made that way disappears if not recorded.

What Changed in This Update

• Provides identity articles explaining how 5BY.AI differs from note apps, summary services, and simple search engines.
• Unpacks the roles of Raw, Pack, Saved, Anchor, Handoff, and Graph View from the user's perspective.
• Records reasons for not making automatic recommendation, automatic importance judgment, and time decay defaults.
• Addresses the problem of thinking flow breaking when using multiple AIs and the value of long-term knowledge preservation.
• Product comparison articles focus on ownership of memory and reentry structure differences rather than feature counts.
• Starting with 32 initial articles, we are continually expanding the archive by reinforcing design and use cases.

How to Verify

1. Select a topic or category of interest at /notes.
2. Before using a feature, check the design background and limitations of that feature.
3. Follow related article links to read identity, features, and use cases together.
4. If the product screen and article descriptions differ, check based on the latest public update and actual behavior.

Example in Actual Usage Flow

For example, to verify this change, the user selects a topic or category of interest at /notes. Before using a feature, they check the design background and limitations of that feature. Then they follow related article links to read identity, features, and use cases together. Finally, if the product screen and article descriptions differ, they check based on the latest public update and actual behavior. In this flow, the following conditions should also be checked. Developer notes do not replace legal terms or permanent product guarantees. Therefore, this update is not just adding one more notice item but enabling the user to check the start, result, and limitations of the feature within the same flow.

Before and After the Change

Before the change, users had to guess this feature or notice from other screens or navigate across multiple pages. After this update, we added a developer notes archive explaining 5BY.AI's identity, memory design, user control principles, and long-term direction that are hard to convey through product features alone. However, items where public notices and actual account/runtime status may differ need to be checked separately, and notice text alone should not be interpreted as expanding permissions or availability.

Scope and Things to Note

• Developer notes do not replace legal terms or permanent product guarantees.
• Unimplemented ideas are not expressed as current features, and confirmed structures and long-term directions are distinguished.
• Changeable or sensitive information like supported Providers, pricing, authentication, and storage policies is not stated definitively without separate verification.
• The purpose of the articles is to disclose 5BY.AI's judgment basis, not to evaluate the user's thoughts.

Why This Change Matters in the Overall 5BY.AI Structure

The developer notes archive is a public record beyond product descriptions where you can check what principles 5BY.AI maintains as it evolves. It becomes a reference point for comparing whether the Core's invariant conditions and user control principles are maintained even as features expand over time.

Criteria for Verifying This Update

• The public screen title, summary, and actual provided feature should describe the same content.
• Adding a new feature should not arbitrarily change existing Saved, Anchor, Handoff, and account flows.
• Conditions that are in preparation or vary by account should be marked separately without exaggerating as fully available.

Related Pages

• Developer Notes Archive
• 5BY.AI's Identity
• Why the User Must Choose Directly
• The Value of the Thinking Process