Why your team's knowledge deserves its own layer

Most tools treat what your team knows as an afterthought — a wiki bolted onto a task manager, a drive folder nobody opens. v2.4 goes the other way: knowledge gets its own layer, with its own structure, and everything else builds on top of it.

Here’s the problem we kept seeing. A team decides something in a meeting. The decision lands in someone’s notes, the context stays in the recording, and the follow-up ends up in a task tool that knows nothing about either. Three months later, someone asks “why did we choose this vendor?” and the answer is scattered across four apps and two people’s memories.

Layer 01, properly built

In 5DAYS, layer 01 is where everything your team has decided, discussed, or documented lives — and v2.4 makes it considerably stronger:

• Hierarchical notes — organize by team, by topic, or both. Notes nest, link, and inherit permissions from their project.
• Connectors — SharePoint, Confluence, OneDrive, and Google Drive documents appear alongside native notes. Connected, not copied: the source stays where it is.
• Transcripts as knowledge — meeting recordings are transcribed in 150+ languages and filed with everything else, searchable word by word.

The point isn’t storage. Plenty of tools store things. The point is that knowledge in layer 01 is structured — it knows which project it belongs to, who can see it, and what came out of it.

Why a separate layer matters

You could throw notes and tasks into one big list. Many tools do. But knowledge and execution behave differently, and mixing them hurts both:

1. Knowledge accumulates; tasks complete. A note from last year can be the most valuable thing in your workspace. A task from last year is usually noise.
2. Knowledge needs context; tasks need status. “Where did this come from?” and “is this done?” are different questions with different interfaces.
3. Knowledge is what AI reasons on. When Spark AI answers a question, it retrieves from layer 01. The cleaner that layer, the better every answer.

That last point is the quiet one. Every improvement to the knowledge layer is an improvement to Spark AI — better retrieval, better grounding, better sources under every claim. A well-kept layer 01 is the difference between an assistant that quotes your actual decisions and one that guesses.

The teams that get the most out of AI aren’t the ones with the best prompts. They’re the ones with the best-organized knowledge.

Getting started with v2.4

If you’re already on 5DAYS, there’s nothing to migrate — your notes, documents, and transcripts are already in layer 01, and the new structure applies to them today. Two things worth doing this week:

• Connect one external source (start with the drive your team actually uses) and watch it show up in search and in Spark AI answers.
• Pick one project and organize its notes hierarchically. It takes ten minutes and it’s the single highest-leverage cleanup in the product.

Your team already produces the knowledge. v2.4 just gives it a place worthy of it.