<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Claude Bezeaud on Medium]]></title>
        <description><![CDATA[Stories by Claude Bezeaud on Medium]]></description>
        <link>https://medium.com/@lbezeaud?source=rss-c4ce46cdce6a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*l75bq4eXNVWe6xKAvh-YnQ@2x.jpeg</url>
            <title>Stories by Claude Bezeaud on Medium</title>
            <link>https://medium.com/@lbezeaud?source=rss-c4ce46cdce6a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:24:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lbezeaud/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[From Photo to Proof: Building a Forensic-Ready Media System]]></title>
            <link>https://medium.com/@lbezeaud/from-photo-to-proof-building-a-forensic-ready-media-system-6768cf2eefc3?source=rss-c4ce46cdce6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6768cf2eefc3</guid>
            <category><![CDATA[osint-investigation]]></category>
            <category><![CDATA[photography]]></category>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <dc:creator><![CDATA[Claude Bezeaud]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 07:30:09 GMT</pubDate>
            <atom:updated>2026-04-07T07:30:09.012Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>From Photo to Proof: Building a Forensic-Ready Media System</strong></p><p>Most photos are just… images.</p><p>They capture a moment, but they don’t prove anything.</p><p>In a world where content can be edited, stripped of metadata, or generated entirely by AI, a simple image is no longer reliable as evidence.</p><p>So the question becomes:</p><p>How do you turn a photo or video into something you can trust?</p><p><strong>The Problem: Images Without Proof</strong></p><p>When you take a photo today, several things happen:</p><ul><li>Metadata may or may not be present.</li><li>- Files can be modified without visible traces.</li><li>- Compression, sharing, or screenshots can alter the original.</li><li>- Hashing alone only proves integrity at a given moment – not origin.</li></ul><p>Even worse:</p><p>If someone sends you a file without metadata and you hash it,</p><p>you are only proving that this version exists, not that it is authentic.</p><p><strong>A Different Approach: The Forensic Model</strong></p><p>Instead of treating media as a file,</p><p>we treat it as a proof object.</p><p>The idea is simple:</p><p>A piece of media should carry its own evidence.</p><p>This leads to a system built on three layers:</p><p><strong>1. Integrity, Has this file been altered ?</strong></p><p>Every package includes:</p><ul><li>A SHA-256 hash of the original file.</li><li>- A hash of the metadata.</li><li>- A canonical manifest containing all elements.</li></ul><p>The manifest itself is hashed, creating a self-consistent structure.</p><p>If anything changes, the chain breaks.</p><p><strong>2. Provenance, Where does this file come from?</strong></p><p>This is where most systems fail.</p><p>Exif data can be removed.</p><p>File names can be changed.</p><p>Context can be lost.</p><p>So instead, we embed identity directly into the media:</p><ul><li>A visible watermark (human-readable proof ID)</li><li>- An invisible watermark (robust, machine-level signal)</li></ul><p>This creates a persistent link between the media and its origin.</p><p>Even if the file is shared, compressed, or renamed,</p><p>the identity remains attached.</p><p><strong>3. Time, When did this exist?</strong></p><p>To anchor the proof in time, we use:</p><ul><li>RFC 3161 timestamps.</li><li>- Applied to the manifest hash, not just the file.</li></ul><p>This ensures that:</p><p>The entire structure (media + metadata + proof chain) existed at a specific moment.</p><p>Not just the image.</p><p><strong>Why Combine These Three?</strong></p><p>Each component alone is not enough:</p><ul><li>Hash → proves integrity, but not origin.</li><li>- Watermark → proves identity, but not time.</li><li>- Timestamp → proves time, but not authenticity.</li></ul><p>Together, they form a coherent chain of trust:</p><p>Who → What → When</p><p><strong>Local, Verifiable, Independent</strong></p><p>A key design choice:</p><p>Verification must not depend on a server.</p><p>Everything needed to verify a package is inside:</p><ul><li>The original file.</li><li>- The manifest.</li><li>- The hashes.</li><li>- The timestamp.</li><li>- The signature.</li></ul><p>This makes the system:</p><ul><li>Durable.</li><li>- Portable.</li><li>- Trust-minimized.</li></ul><p><strong>Real-World Use Cases</strong></p><p>This is not theoretical.</p><p>A forensic-ready media system can be used for:</p><ul><li>Documenting incidents.</li><li>- Protecting authorship.</li><li>- Providing proof in disputes.</li><li>- Ensuring traceability of media.</li></ul><p>Not every photo needs this.</p><p>But when it matters, it really matters.</p><p><strong>A Shift in Perspective</strong></p><p>We don’t need better images.</p><p>We need trustworthy images.</p><p>The future of media is not just about quality or realism.</p><p>It’s about verifiability.</p><p>Turning a photo into proof is not a feature.</p><p>It’s a different way of thinking about media altogether.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6768cf2eefc3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Productivity tools ignore mental reality – and that’s the real problem]]></title>
            <link>https://medium.com/@lbezeaud/productivity-tools-ignore-mental-reality-and-thats-the-real-problem-52fe504f15c2?source=rss-c4ce46cdce6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/52fe504f15c2</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[iphone]]></category>
            <dc:creator><![CDATA[Claude Bezeaud]]></dc:creator>
            <pubDate>Mon, 29 Dec 2025 11:59:41 GMT</pubDate>
            <atom:updated>2025-12-29T11:59:41.750Z</atom:updated>
            <content:encoded><![CDATA[<p>Productivity apps are everywhere. They promise clarity, control, and peace of mind. Yet for many people, they end up doing the opposite. Instead of reducing anxiety, they amplify it.</p><p>The issue is rarely a lack of features. Modern tools are powerful, polished, and technically impressive. The real problem lies elsewhere, in the gap between objective workload and mental capacity.</p><p>Mental reality is not motivation, discipline, or willpower. It is the real workload projected into an emotionally acceptable perspective. Time does not change. Deadlines do not change. What changes is how much of that reality a person can carry without breaking.</p><p>Most productivity systems ignore this. They expose everything at once: all tasks, all projects, all deadlines, all the time. They assume linear thinking and emotional neutrality. The result is not clarity, but cognitive overload.</p><p>Some tools choose strict determinism, enforcing rigid workflows and rules. Others choose extreme simplicity, stripping everything down to basic lists. Both approaches miss the same point. The tool should adapt to the mind, not force the mind to adapt to the tool.</p><p>Scopit was built around this conviction. Its core principle is simple: the app adapts to mental reality, not the other way around. Instead of infinite lists, it relies on time-based perspectives. Instead of total exposure, it uses intentional visibility windows. Instead of pressure and guilt, it favors clarity and continuity.</p><p>The goal is not to optimize productivity in the abstract. It is to make progress possible without emotional overload. When the perspective becomes acceptable, action becomes natural again.</p><p>Being productive should not feel like carrying a permanent weight. A good system does not ask why you are not doing enough. It asks what you can realistically handle right now.</p><p>The future of productivity tools is not smarter automation or more features. It is emotional alignment. When a tool respects mental reality, it stops being a source of anxiety and becomes a support.</p><p>That is the space Scopit is trying to occupy.</p><p>The real question is not how much we can do. It is how much we can see without collapsing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52fe504f15c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Broken Contract Between Productivity Tools and Their Users]]></title>
            <link>https://medium.com/@lbezeaud/the-broken-contract-between-productivity-tools-and-their-users-414b6721a0d7?source=rss-c4ce46cdce6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/414b6721a0d7</guid>
            <category><![CDATA[productivity-tools]]></category>
            <category><![CDATA[productivity-apps]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Claude Bezeaud]]></dc:creator>
            <pubDate>Sun, 21 Dec 2025 17:26:30 GMT</pubDate>
            <atom:updated>2025-12-21T17:26:30.579Z</atom:updated>
            <content:encoded><![CDATA[<p>Most people don’t fail at productivity because they lack motivation, discipline, or the right method.</p><p>They fail because at some point, the volume of unfinished actions and future obligations exceeds what the human mind can comfortably hold. When that happens, the brain does what it has always done: it looks for external support. A list. A notebook. An app.</p><p>Choosing a productivity tool is rarely a neutral act. It is a quiet decision to share the load. We offload memory, structure, and perspective with the implicit expectation that things will move forward more smoothly.</p><p>What we rarely acknowledge is that this choice creates an informal contract between the user and the tool. Not a legal one, but a psychological one. An association of means, with an unspoken obligation of outcome.</p><p>And when that outcome doesn’t materialize, the failure is almost always internalized by the user.</p><p>We call it procrastination.</p><p>The Broken Contract Between Productivity Tools and Their Users</p><p>Most productivity problems don’t start with laziness or poor discipline. They start when the human brain can no longer hold the growing volume of unfinished actions and future obligations</p><p>At that point, we look for relief. Lists. Checkboxes. A notebook. A “better” app. This is a natural response, and in truth, almost any system can work when it comes to capturing tasks.</p><p>The real problem appears later, in the relationship between the human and the tool.</p><p>Between the user and a productivity system exists an informal but very real contract. By choosing a tool, the user is not just storing tasks – they are entering an association of means. The user brings intention, attention, and effort. The tool brings structure, memory, and perspective. Together, they implicitly carry an obligation of outcome: things are expected to move forward.</p><p>This contract cannot be fulfilled by either side alone. The user cannot resolve the problem without external structure. The tool cannot produce results without human action.</p><p>Yet when nothing moves, the failure is experienced almost exclusively on the human side. The contract feels broken, but only the user pays the emotional cost. Guilt appears. Self-blame follows. We call this procrastination, even though it is often the symptom of a contract that has become unbalanced.</p><p>Most productivity systems break not because they lack features, but because they silently abandon the user once execution becomes difficult. They continue to store, remind, and display – but they stop sharing responsibility for outcomes.</p><p>A tool that truly helps does not promise control. It acknowledges the contract. It actively supports the user when the obligation of result becomes heavy, instead of leaving them alone with it.</p><p>If productivity systems continue to fail, it is not because humans are broken, nor because tools are inherently flawed. It is because the contract between them is rarely acknowledged, and almost never honored on both sides.</p><p>A fair contract does not promise control, discipline, or constant motivation. It recognizes that execution is fragile, uneven, and deeply human. It accepts that there will be resistance, hesitation, and moments where intention alone is not enough.</p><p>In such a contract, the tool does more than store and remind. It actively carries part of the cognitive and emotional load when action becomes difficult. It helps narrow focus, reduce pressure, and restore perspective, instead of silently accumulating evidence of failure.</p><p>When responsibility is shared, guilt has less room to grow. Progress no longer depends on heroic effort, but on continuity and support.</p><p>Productivity, in the end, is not about doing more. It is about not being left alone when doing becomes hard.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=414b6721a0d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s coming to Scopit]]></title>
            <link>https://medium.com/@lbezeaud/whats-coming-to-scopit-9feed25576ef?source=rss-c4ce46cdce6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9feed25576ef</guid>
            <category><![CDATA[productivity-tools]]></category>
            <category><![CDATA[iphone]]></category>
            <category><![CDATA[notetaking]]></category>
            <category><![CDATA[productivity-apps]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Claude Bezeaud]]></dc:creator>
            <pubDate>Fri, 19 Dec 2025 20:38:28 GMT</pubDate>
            <atom:updated>2025-12-19T20:38:28.385Z</atom:updated>
            <content:encoded><![CDATA[<p>A quiet step forward, focused on clarity rather than complexity.</p><p>Scopit was built around a simple belief: clarity doesn’t come from doing more, but from understanding what your time is already asking of you.</p><p>From the beginning, Scopit has not treated tasks as items to be completed, but as engagements moving through time. Inbox, Today, Upcoming, Past, Pinned – not as categories, but as states.</p><p>What’s coming next builds quietly on that foundation. Not a new layer of features. Not an AI that talks. But a system that listens more carefully.</p><p>Most productivity tools focus on organization. Scopit focuses on trajectories: what enters your Inbox, what keeps being postponed, what never quite finds its moment, what actually gets lived. These movements form patterns. And those patterns often say more than plans or intentions. The next step for Scopit is to help surface that story – gently, without noise.</p><p>Scopit is exploring intelligence as perception, not automation. Instead of generating content or telling you what to do, the system quietly observes recurring drift, stalled intentions, routines that no longer serve a purpose, and moments where a decision is needed rather than another reschedule. The goal is not to optimize your days. It’s to reduce friction and mental weight.</p><p>What’s coming will remain restrained: subtle prompts, optional reflections, gentle suggestions. No scores. No productivity metrics. No judgment. Scopit won’t interrupt your flow. It will simply offer clearer signals, when they matter.</p><p>These ideas are being introduced carefully, in small steps. Nothing experimental will be forced into your daily workflow. Each addition must earn its place by being useful, calm, and predictable. This is not a promise of features. It’s a commitment to direction.</p><p>Scopit will continue to evolve as a companion to your time – helping you notice what matters, and letting go of what quietly doesn’t. More details will come when they’re ready. Until then, Scopit remains focused on what it already does best: bringing clarity and calm to the way time is lived.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9feed25576ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Productivity Is Not a Sport. It’s Attention Hygiene.]]></title>
            <link>https://medium.com/@lbezeaud/productivity-is-not-a-sport-its-attention-hygiene-ec3c86b4aac4?source=rss-c4ce46cdce6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec3c86b4aac4</guid>
            <category><![CDATA[second-brain]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[productivity-tools]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[productivity-apps]]></category>
            <dc:creator><![CDATA[Claude Bezeaud]]></dc:creator>
            <pubDate>Mon, 15 Dec 2025 20:53:21 GMT</pubDate>
            <atom:updated>2025-12-15T20:53:21.323Z</atom:updated>
            <content:encoded><![CDATA[<p>Productivity Is Not a Sport. It’s Attention Hygiene.</p><p>For a long time, I thought I had an organization problem. What I actually have is a mental load problem.</p><p>Not the weight of actions themselves, but the weight of everything that has to remain mentally active. Contexts, unfinished thoughts, things to prepare, things not to forget, things that will matter later. What drains energy is not execution. It is keeping too many things suspended in the mind.</p><p>Most productivity apps are not bad. They are simply built for a very specific kind of user. People with clean workflows, stable roles, clearly separated contexts, and enough mental bandwidth to maintain the system itself. These tools often grow by adding features, views, rules, and options. Over time, they do what they can, not necessarily what they should: protect attention.</p><p>For some people, this works perfectly. For others, the tool becomes another responsibility. Something that needs care, discipline, and constant maintenance just to remain useful.</p><p>I am not a startup founder. I am not chasing hustle or scale. I simply have several small activities running in parallel. Each one is manageable on its own, but together they fragment attention. The problem is not motivation or effort. The problem is cognitive context switching.</p><p>What I need is not more structure. What I need is relief.</p><p>A few years ago, I would never have started building yet another checklist app. Without assistance, productivity systems tend to become rigid and demanding. They assume that the user will always be disciplined enough for the system to work. That assumption breaks down quickly in real life.</p><p>Artificial intelligence changed that equation for me. Not because it can decide for us, and not because it can automate life, but because it can reduce vigilance. It can help surface forgotten context, reconnect related things, and gently remind without demanding constant attention. Used carefully, AI is not a feature. It is cognitive assistance.</p><p>I am not trying to invent a new philosophy, and I am not trying to compete with existing methods. Every system has its users, and that is perfectly fine. What I want is to speak to people who often feel invisible in this space. People who struggle to organize not because they lack discipline, but because their mental load outweighs their capacity. People for whom productivity tools sometimes add weight instead of removing it.</p><p>I have a hard time believing I am alone in seeing things this way. The conversations already exist, scattered across forums, comment sections, and private notes. They simply do not have a clear place to gather.</p><p>Yes, if the goal is to make a lot of money on the App Store, the safest path is to build a game. That is not my path. I am building something useful, sustainable, and deliberately niche. Something for people who want to think more clearly, not perform productivity.</p><p>If this resonates with you, if organization feels heavier than the goals it is supposed to support, if attention is your real bottleneck, I would genuinely like to hear how you navigate this. Not to sell anything. Just to connect with others who are carrying the same invisible weight.</p><p>Claude.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec3c86b4aac4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Scopit Introduces AI: Simple, Local, and Truly Useful]]></title>
            <link>https://medium.com/@lbezeaud/how-scopit-introduces-ai-simple-local-and-truly-useful-a0e8ef5de863?source=rss-c4ce46cdce6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0e8ef5de863</guid>
            <category><![CDATA[productivity-tools]]></category>
            <category><![CDATA[productivity-hacks]]></category>
            <category><![CDATA[productivity-apps]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Claude Bezeaud]]></dc:creator>
            <pubDate>Thu, 11 Dec 2025 13:08:34 GMT</pubDate>
            <atom:updated>2025-12-11T13:24:44.136Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*zTzylywPngH5zzXOxSxl8g@2x.jpeg" /></figure><p>AI is appearing everywhere in productivity apps: chatbots, auto-generated tasks, predictive planning…</p><p>But the problem is always the same:</p><p>If AI adds cognitive load, it stops being helpful.</p><p>At Scopit, we took the opposite direction.</p><p>We are introducing our first piece of AI – fully local, no network connection required – with a very simple goal:</p><p>Help you choose ONE realistic action for today.</p><p>Nothing more.</p><p>Nothing overwhelming.</p><p>Just clarity.</p><p>⸻</p><p>Why AI Must Stay Simple</p><p>Most productivity tools try to solve complexity by… adding more complexity:</p><p>•	more fields,</p><p>•	more options,</p><p>•	more choices,</p><p>•	more automation that quickly becomes noise.</p><p>The result?</p><p>People procrastinate because the system itself becomes too heavy.</p><p>Scopit starts from a different truth:</p><p>Time is stable, rare, and readable. Tasks are not.</p><p>AI should reveal what matters today – not create another layer of abstraction.</p><p>⸻</p><p>Daily Focus: Move Forward Without Burning Out</p><p>The first AI feature inside Scopit is intentionally minimalistic:</p><p>a Daily Focus suggestion, generated locally from your current day.</p><p>It does not replace your judgement.</p><p>It does not take control.</p><p>It simply highlights one meaningful direction:</p><p>•	an overdue task you can unblock,</p><p>•	an undated item that deserves attention,</p><p>•	or a planned action that needs clarification.</p><p>The goal isn’t to do more.</p><p>It’s to move forward – calmly and consistently.</p><p>A powerful approach for users overwhelmed by long lists.</p><p>⸻</p><p>Why Local Instead of Cloud AI?</p><p>Because a daily assistant must be:</p><p>•	reliable, even offline,</p><p>•	respectful, keeping your data on your device,</p><p>•	instant, with no network delay,</p><p>•	predictable, not dependent on external model changes.</p><p>This first AI module is deliberately light and deterministic —</p><p>no chat, no large model, no surprises.</p><p>It does one job, does it well,</p><p>and stays out of your way.</p><p>⸻</p><p>Three Ways to Set Your Daily Focus</p><p>Scopit never forces a workflow.</p><p>You remain in control at all times.</p><p>You can set the Daily Focus via:</p><p>1.	Local AI suggestions, through a dedicated sheet.</p><p>2.	Long press on any event → “Set as Today’s Focus”.</p><p>3.	Manual selection, even if AI is disabled in settings.</p><p>This flexibility is intentional:</p><p>your day, your rules.</p><p>⸻</p><p>An AI That Respects Your Autonomy</p><p>Scopit’s AI:</p><p>•	does not create tasks,</p><p>•	does not guess your life,</p><p>•	does not over-interpret your data,</p><p>•	does not judge or nudge you aggressively.</p><p>It suggests, and you choose.</p><p>A healthy relationship between user and tool —</p><p>not a system that tries to run your life.</p><p>⸻</p><p>What’s Next?</p><p>This first step lays the foundation for a broader vision:</p><p>•	fully local AI, evolving with your habits,</p><p>•	periodic check-ins,</p><p>•	subtle detection of procrastination patterns,</p><p>•	resurfacing forgotten notes,</p><p>•	smart perspective building,</p><p>•	all while keeping you in control.</p><p>No hype.</p><p>No over-automation.</p><p>Just thoughtful assistance that strengthens your clarity.</p><p>⸻</p><p>Conclusion: AI as the Missing Link in Scopit’s Time Model</p><p>Scopit isn’t just another task app.</p><p>It’s a time-based system, where clarity comes first.</p><p>This first AI module doesn’t try to reinvent productivity.</p><p>It simply connects the dots between your intentions and your reality —</p><p>with subtle, respectful, and local intelligence.</p><p>Not spectacular.</p><p>But deeply useful.</p><p>And exactly the kind of AI we want to build.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0e8ef5de863" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A task is not a checkbox]]></title>
            <link>https://medium.com/@lbezeaud/a-task-is-not-a-checkbox-01c136cce12a?source=rss-c4ce46cdce6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/01c136cce12a</guid>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[pkm]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[productivity-apps]]></category>
            <dc:creator><![CDATA[Claude Bezeaud]]></dc:creator>
            <pubDate>Mon, 08 Dec 2025 11:54:07 GMT</pubDate>
            <atom:updated>2025-12-08T11:54:07.982Z</atom:updated>
            <content:encoded><![CDATA[<p>A more honest way to think about “events”, with Scopit</p><p>⸻</p><p>We love tools.</p><p>A new todo app, a magical template, a “revolutionary” productivity method…</p><p>We tell ourselves that this time, it will finally feel clear, fluid, under control.</p><p>And then, as usual, something breaks.</p><p>Tasks pile up. Some become invisible. Others stay there for weeks. We start avoiding the system, writing things somewhere else, or quietly giving up “for now”. The tool itself may not be bad, but it doesn’t deliver what it promised.</p><p>I ended up with a simple, slightly uncomfortable conclusion:</p><p>No system works without commitment.</p><p>And as long as we don’t know what a task really is, no app can save us.</p><p>That’s why, in Scopit, I wanted to redefine what an event actually is.</p><p>⸻</p><p>The default model: task = checkbox</p><p>Most systems implicitly behave like this:</p><p>A task = a title + a due date + a checkbox</p><p>Typical example:</p><p>•	Title: “Pay the electricity bill”</p><p>•	Date: tomorrow</p><p>•	Status: to-do → done → archived</p><p>This model works reasonably well for simple, imperative items:</p><p>pay a bill, call someone before a deadline, show up at a meeting.</p><p>It falls apart everywhere else:</p><p>•	fuzzy projects: “Redesign the website”</p><p>•	ambitions: “Write a book someday”</p><p>•	important but non-urgent things: “Explore a career change”, “Prepare 2026 offers”, etc.</p><p>We throw these into the system without really defining them, without a horizon, without context.</p><p>The result is very common: even with a good tool, we mostly end up managing a graveyard of undecided stuff.</p><p>⸻</p><p>What if a task was more than just “something to do”?</p><p>In Scopit, I ended up adopting a different point of view:</p><p>A task (or rather, an event) is not just “something to do”.</p><p>It’s a structured commitment in time, with enough context for my future self to act on it.</p><p>Concretely, a Scopit event rests on four dimensions:</p><p>1.	A title – what I’m committing to.</p><p>2.	A projection in time – dated or undated.</p><p>3.	A perspective – at what horizon it’s realistic.</p><p>4.	An execution context – what I’ll need when the time comes.</p><p>We stay in something simple, but we finally move beyond “one line in a list”.</p><p>⸻</p><ol><li>A title: clearly identifying the commitment</li></ol><p>It sounds trivial. It isn’t.</p><p>Titles like:</p><p>•	“John”</p><p>•	“Website”</p><p>•	“Book project”</p><p>…don’t help anyone, especially not the version of you reading this again in two weeks.</p><p>In Scopit, the title is the mental handle. It should answer a very simple question:</p><p>“If I see this again in a month, will I still understand what it’s about?”</p><p>Examples:</p><p>•	“Call John to confirm the video quote before Friday”</p><p>•	“List the 3 main sections for the new home page”</p><p>•	“Draft a rough outline for chapter 1 (without aiming for quality yet)”</p><p>It’s not poetry. It’s a small contract.</p><p>⸻</p><p>2. A projection: where does it live in time?</p><p>There are two legitimate possibilities.</p><p>Case 1: the event is dated</p><p>The event is anchored to a specific day (and optionally a time, a reminder, a repeat rule).</p><p>Perfect for:</p><p>•	hard deadlines</p><p>•	appointments</p><p>•	actions that truly belong to one day</p><p>Case 2: the event is undated</p><p>The event matters, but you’re not ready to put it on the calendar yet.</p><p>This is exactly where most systems collapse: everything undated falls into an endless “later”.</p><p>Scopit doesn’t just store these floating items.</p><p>We add something on top.</p><p>⸻</p><p>3. A perspective: at what horizon is it realistic?</p><p>This is one of the most important bricks in the model.</p><p>When an event is undated, we don’t stop at “someday”.</p><p>We give it a perspective:</p><p>•	this month</p><p>•	this quarter</p><p>•	this year</p><p>•	someday / later</p><p>In practice, this changes a lot:</p><p>You’re no longer saying “I’ll do this someday”,</p><p>you’re saying “this is not for this week – it’s more of a quarterly thing”</p><p>or “this clearly belongs to this year, not this month”.</p><p>The gesture is tiny, but it breaks one of the biggest traps in task systems:</p><p>the permanent mix between what should be on your radar now and what shouldn’t even be visible today.</p><p>⸻</p><p>4. A context: how will I actually do it when the time comes?</p><p>Finally, an event is not just a line in a list.</p><p>It also includes:</p><p>•	Notes – why it matters, what’s blocking, decisions already made, open questions</p><p>•	Subtasks – the ability to break it down into concrete steps as you get closer</p><p>•	A domain – work, personal, etc., to filter and focus</p><p>•	Tags – topics, projects, contexts (#bills, #studio, #family…)</p><p>•	Links – documents, webpages, related notes, internal deep links…</p><p>The more an event resists, the more it deserves to be enriched.</p><p>That’s not a failure. It’s a sign that you’re turning a vague idea into something doable.</p><p>⸻</p><p>Two concrete examples: dated vs undated</p><p>Let’s make this less abstract.</p><p>Example 1: a dated event</p><p>Classic case: paying a bill.</p><p>•	Title</p><p>“Pay January electricity bill (EDF)”</p><p>•	Projection</p><p>Date: January 28</p><p>Reminder: the day before at 6pm.</p><p>•	Perspective</p><p>Not really needed here – the deadline is already clear and near.</p><p>•	Context</p><p>•	Note: “Bill received by email on Jan 5. Around 120€.”</p><p>•	Link: to the PDF or client area.</p><p>•	Tag: #bills, Domain: “Personal”.</p><p>When this shows up in Today, you don’t think:</p><p>“What is this again? What am I supposed to do? Where’s the document?”</p><p>It’s all right there.</p><p>⸻</p><p>Example 2: an undated event with perspective</p><p>Trickier case: a project you genuinely care about, but not right now.</p><p>•	Title</p><p>“Prepare a bilingual version of the website for next year”</p><p>•	Projection</p><p>Undated: it’s clearly not for this week or this month.</p><p>•	Perspective</p><p>“This year”: you decide it should stay somewhere in this year’s horizon, but not in the short term.</p><p>•	Context</p><p>•	Note:</p><p>•	“Goal: have the website FR/EN before next fall.”</p><p>•	“To clarify: number of pages, translation budget, tone of voice in English.”</p><p>•	Subtasks:</p><p>1.	List all current pages</p><p>2.	Choose what really needs translation</p><p>3.	Test 2 – 3 translators or tools</p><p>•	Tags: #website, #marketing</p><p>•	Domain: “Work”.</p><p>This event will not pollute your Today view.</p><p>It will reappear when you think at the “this year” level, or in your undated view.</p><p>But when it does, you’re not starting from scratch: the context, first steps and horizon are already there.</p><p>⸻</p><p>What the tool will never do for you</p><p>We’d all love a magical app that:</p><p>•	understands the importance of each task</p><p>•	sorts them automatically</p><p>•	schedules them</p><p>•	and gently walks us to completion</p><p>In reality:</p><p>The tool can’t replace the user’s minimal commitment.</p><p>It can only make that commitment simpler, lighter, and more pleasant.</p><p>In Scopit, this minimal commitment looks like:</p><p>1.	Giving an honest title to what you want to do.</p><p>2.	Deciding whether it’s dated or undated.</p><p>3.	Choosing a realistic horizon (this month, this quarter, this year, later).</p><p>4.	Adding a bit of context when it’s needed.</p><p>This doesn’t guarantee everything will get done.</p><p>But it does guarantee one thing: you won’t be staring at a list of ghosts you don’t even remember writing.</p><p>⸻</p><p>What this changes in an app like Scopit</p><p>In the interface, this model becomes:</p><p>•	event cards that show more than a title and a date: perspective, subtasks, linked note, tags, links…</p><p>•	a Today view that distinguishes what’s truly within reach,</p><p>instead of mixing everything into one anxious feed</p><p>•	a space for undated items that isn’t a pure graveyard,</p><p>because each one is anchored to a perspective (month, quarter, year, later)</p><p>And above all:</p><p>a model you can explain to a user without turning it into a productivity factory.</p><p>⸻</p><p>Conclusion: a system is only useful if we accept this minimum of commitment</p><p>We can spend our lives trying apps, methods, frameworks.</p><p>In the end, it comes down to two things:</p><p>1.	Accepting a small minimum of commitment in how we capture events.</p><p>2.	Having a tool that respects that commitment instead of diluting it.</p><p>Scopit is not a “productivity ON” magic switch.</p><p>It’s a concrete attempt to answer a simple question:</p><p>“How can we represent an event in a way that’s rich enough to be actionable,</p><p>without becoming unmanageable?”</p><p>For now, the answer fits into four bricks:</p><p>Title, Projection, Perspective, Context.</p><p>It’s not much.</p><p>But it’s often exactly what’s missing for the things we write down to have a chance to actually happen.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=01c136cce12a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We Don’t Need Another Productivity App]]></title>
            <link>https://medium.com/@lbezeaud/we-dont-need-another-productivity-app-9d2168b10a90?source=rss-c4ce46cdce6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d2168b10a90</guid>
            <category><![CDATA[pkm]]></category>
            <category><![CDATA[productivity-apps]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[note-taking-app]]></category>
            <category><![CDATA[notetaking]]></category>
            <dc:creator><![CDATA[Claude Bezeaud]]></dc:creator>
            <pubDate>Fri, 05 Dec 2025 09:14:14 GMT</pubDate>
            <atom:updated>2025-12-05T09:14:14.764Z</atom:updated>
            <content:encoded><![CDATA[<p>Towards a clearer, kinder relationship to time – and an open model you’re invited to challenge.</p><p>For years, we’ve watched the same cycle repeat itself: new tools, new methods, new buzzwords. Bullet journaling. GTD. Time blocking. Second brains. Apps “for ADHD brains.” Task managers with karma, flames, streaks, badges and dashboards.</p><p>Some of these ideas are brilliant. Many are genuinely helpful.</p><p>But somewhere along the way, a lot of us started to feel the same thing:</p><p>There are more tools than ever…</p><p>and yet our time doesn’t feel much clearer.</p><p>This article is not a pitch for “the ultimate system.”</p><p>It’s a kind of open-source manifesto of intent: the mental model we’re trying to build into our app, Scopit, and an invitation to question it, challenge it, and adapt it.</p><p>We don’t start from scratch.</p><p>We stand on the shoulders of the people and tools who came before us.</p><p>We just try to use that height to see time a little differently.</p><p>⸻</p><ol><li>From deadlines to a model of time</li></ol><p>We started from something very simple: counting down to dates.</p><p>Originally, our work revolved around the idea of an upcoming event, a deadline, a date that matters. Think of it as:</p><p>“I have an important moment in the future.</p><p>Let me see it coming, feel it approaching, and prepare for it.”</p><p>That was the seed.</p><p>But once you spend enough time with deadlines, something becomes obvious: they don’t exist in isolation. They sit inside a continuum of time:</p><p>•	today</p><p>•	the next few days and weeks</p><p>•	the further future</p><p>•	the things without a date (but not without importance)</p><p>•	the traces of what has already happened</p><p>So gradually, we moved from:</p><p>an app centered on deadlines</p><p>to:</p><p>a model of how we inhabit time.</p><p>That shift changed everything.</p><p>We stopped asking only: “What’s due when?”</p><p>And started asking: “Where does this belong in my lived time?”</p><p>⸻</p><p>2. What we’re pushing against</p><p>We don’t think the current productivity landscape is “bad.”</p><p>We think it’s noisy.</p><p>On un côté, we find:</p><p>•	ultra-minimal apps, often branded as “ADHD-friendly”, with gentle pastel palettes, big buttons and as little structure as possible. They can be comforting, but sometimes they stay too shallow.</p><p>On the other side:</p><p>•	powerful, intricate systems with projects, contexts, tags, areas, templates, routines, dashboards, automations. Amazing for some people, but often intimidating or guilt-inducing for others.</p><p>Somewhere between the two:</p><p>•	tools that turn your life into a game: streaks, achievement levels, karma points, “you did less than last week” messages.</p><p>We are trying to go in a different direction:</p><p>•	No moral judgment on your output.</p><p>No “you could have done more”, no streak shame, no productivity scoreboard.</p><p>•	No worship of complexity.</p><p>You shouldn’t need a handbook or a course to understand how to use your own time.</p><p>•	No dopamine tricks to keep you hooked.</p><p>If our tool only works when it flatters or pressures you, it’s not really helping.</p><p>We’re not against minimalism, or structure, or even gamification in general.</p><p>We just believe the core problem is somewhere else:</p><p>Most people don’t need to be maximally productive.</p><p>They need their time to become readable.</p><p>⸻</p><p>3. Open source → open mind</p><p>We came to this project with a simple conviction:</p><p>Knowledge is universal.</p><p>Methods are shared.</p><p>Nobody “owns” the concept of how to organize time.</p><p>So instead of pretending to invent a method from nothing, we choose another stance:</p><p>•	We acknowledge our influences: GTD, calendars, time blocking, minimalist task managers, ADHD-friendly apps – we’ve been shaped by all of them.</p><p>•	We reuse ideas when they work, and we adapt them when they don’t.</p><p>•	We don’t hide our thinking. The model is not secret sauce. It’s something we’re happy to expose, question, even break.</p><p>That’s what we mean by open mind:</p><p>•	Like open source, but for mental models.</p><p>•	The “code” here is the way we structure time, not the Swift behind the UI.</p><p>•	The “license” is simple: discuss it, fork it, disagree with it, improve it.</p><p>We don’t claim to have The Method.</p><p>We have a version 1.0 of a shared reflection, and we’re making it public.</p><p>⸻</p><p>4. A simple model of time (that tries to go deep, not wide)</p><p>Our brique principale is not a feature.</p><p>It’s a structure.</p><p>We try to see time through a few core lenses:</p><p>•	Today</p><p>What truly belongs to this day? What is on stage now?</p><p>•	Upcoming</p><p>What’s approaching soon enough that it needs to be in my field of view?</p><p>•	Further ahead</p><p>The things that matter, but whose time hasn’t really started yet.</p><p>•	Without a date</p><p>Not “someday/maybe” in the sense of “probably never”, but:</p><p>“This exists, it matters, it just doesn’t have a slot in time yet.”</p><p>•	Perspective (month / quarter / year)</p><p>A way of saying:</p><p>“I won’t do this now, but I make a gentle promise to my future self:</p><p>I’ll revisit it in this time horizon.”</p><p>•	Past and accomplishments</p><p>Not to measure “how good” you were, but to keep a trace of what you’ve actually lived and done – without turning it into a performance report.</p><p>We don’t pretend this is revolutionary.</p><p>What matters is how it feels in practice:</p><p>•	instead of an infinite bucket of “someday” tasks that become a graveyard,</p><p>•	we want floating items that can be anchored into perspective (month/quarter/year) when the time is right.</p><p>•	instead of a pure wall of “overdue” guilt,</p><p>•	we want context: what really needs to move, what can be reframed, what can be consciously dropped.</p><p>We’re less interested in making you do more, and more interested in helping you see more clearly:</p><p>This is what is on my plate now.</p><p>This is quietly waiting in the wings.</p><p>This is a promise I make to my future self.</p><p>This has had its time – and it’s okay to let it go.</p><p>⸻</p><p>5. Our relationship to technique (and why AI matters here)</p><p>We want to be honest about how this project exists at all.</p><p>We don’t come from the “pure developer” route in the traditional sense.</p><p>There is no formal computer science background behind this manifesto.</p><p>For a long time, the process looked like this:</p><p>We have a problem → we search → we read → we adapt → we ship.</p><p>The internet was our teacher.</p><p>Blogs, Stack Overflow, documentation: just-in-time learning.</p><p>That approach works surprisingly well…</p><p>…until the ** industrial pace of technology** catches up with you:</p><p>•	frameworks that evolve constantly,</p><p>•	new APIs every year,</p><p>•	big architectural shifts,</p><p>•	and an endless stream of “best practices” to keep up with.</p><p>For a solo maker, this “industrial-level” tech evolution can become overwhelming.</p><p>It’s not just about skills anymore.</p><p>It’s about time, energy, and attention.</p><p>That’s exactly where AI changes the equation for us.</p><p>We don’t use AI to replace thinking.</p><p>We use it to bridge the gap between our vision and the technical reality required to build it:</p><p>•	to translate intentions into code,</p><p>•	to debug obscure errors without losing a day,</p><p>•	to explore alternatives quickly,</p><p>•	to stay focused on what we care about most:</p><p>the model of time, the user experience, the clarity we want to offer.</p><p>The code still matters.</p><p>Quality still matters.</p><p>But they are not the center of the project.</p><p>The center is our relationship to time.</p><p>The technology exists so that this relationship can be explored, not the other way around.</p><p>If AI can allow more people to bring their ideas to life without becoming full-time experts in every framework and tool, we think that’s a good thing.</p><p>⸻</p><p>6. Why we speak in “we”</p><p>You may have noticed it already: we write in “we”, not “I”.</p><p>That’s not a rhetorical trick.</p><p>It reflects how we see this work.</p><p>Behind these words, there isn’t a productivity guru on a stage, explaining the right way to live. There is:</p><p>•	a journey,</p><p>•	a lot of trial and error,</p><p>•	influences from other apps and methods,</p><p>•	late-night experiments,</p><p>•	conversations with early users,</p><p>•	and now: you, if you’re reading this.</p><p>We speak in “we” because:</p><p>•	we build on the work of those who came before us,</p><p>•	we rely on technologies that are themselves collective achievements,</p><p>•	and we want this model to be shaped by the people who use it, question it, bend it to their reality.</p><p>This project is not the voice of one individual.</p><p>It’s a conversation in progress.</p><p>“Nous” includes users, critics, predecessors, and the tools themselves (yes, including AI) that help us turn ideas into something you can touch.</p><p>⸻</p><p>7. The quiet influence of a small personal pantheon</p><p>Every creator has a private pantheon – people who quietly shape the way they think.</p><p>In ours, two names have had a strong influence:</p><p>•	Steve Jobs, for the obsession with end-to-end experience.</p><p>Not technology for its own sake, but technology that disappears behind what it enables you to feel and do.</p><p>•	Sam Altman, for the idea of building enabling platforms: creating something that doesn’t just solve one problem, but unlocks the ability for many others to create.</p><p>We are not trying to mimic them.</p><p>But we recognize a simple line that runs through their work:</p><p>Technology should expand what humans can do,</p><p>not bury them under its complexity.</p><p>At our tiny scale, that’s what we’re trying to honor:</p><p>•	through the experience we craft around time (a little bit of Jobs),</p><p>•	and through the way we use AI and modern tools to make this experience possible at all (a little bit of Altman).</p><p>⸻</p><p>8. An invitation, not a doctrine</p><p>This text is not a manual.</p><p>We are not saying:</p><p>•	“Here is the one true way to organize your time.”</p><p>•	“If you don’t use our model, you’re doing it wrong.”</p><p>What we’re saying is closer to:</p><p>“Here is how we currently see the problem.</p><p>Here is the model we’re building into our tool.</p><p>Here are our biases and our choices.</p><p>What do you see that we don’t?”</p><p>We hope this manifesto can:</p><p>•	Inform: make our intentions explicit and transparent.</p><p>•	Spark debate: some will agree, others will push back – both are valuable.</p><p>•	Invite contribution: not necessarily in code, but in perspective:</p><p>“In my life, time feels more like this…”</p><p>In practice, that could look like:</p><p>•	comments, messages, emails,</p><p>•	feature requests anchored in your reality,</p><p>•	critiques of where our model feels off, incomplete, or naive,</p><p>•	completely different ways of mapping time that we haven’t considered.</p><p>We don’t expect consensus.</p><p>We do hope for friction that stays constructive.</p><p>⸻</p><p>9. So, what now?</p><p>If any of this resonates with you – or irritates you in an interesting way – you’re already part of the experiment we’re running.</p><p>We’ll keep:</p><p>•	refining the app,</p><p>•	simplifying the surface,</p><p>•	deepening the model underneath,</p><p>•	and sharing more openly how we think about time, attention, and commitments.</p><p>This manifesto is version 1.0.</p><p>Like any good version, it will:</p><p>•	evolve,</p><p>•	be refactored,</p><p>•	sometimes be contradicted by reality.</p><p>And that’s fine.</p><p>Because the goal is not to be right forever.</p><p>The goal is to build, step by step, a clearer, kinder relationship to time – for ourselves, and for the people who choose to walk with us for a while.</p><p>If you want to follow or challenge this journey, you’re more than welcome.</p><p>We’re not looking only for “users.”</p><p>We’re looking for people who want to think about time with us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d2168b10a90" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Scopit inbox just got faster]]></title>
            <link>https://medium.com/@lbezeaud/the-scopit-inbox-just-got-faster-651efca26488?source=rss-c4ce46cdce6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/651efca26488</guid>
            <category><![CDATA[productivity-apps]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Claude Bezeaud]]></dc:creator>
            <pubDate>Wed, 03 Dec 2025 18:59:22 GMT</pubDate>
            <atom:updated>2025-12-03T18:59:22.767Z</atom:updated>
            <content:encoded><![CDATA[<p>We all know the feeling: you catch an idea or a commitment in your head – “call Alex tomorrow”, “renew insurance before the 15th”, “pay rent on Friday” – and there’s a tiny moment of friction.</p><p>Which app do I open?</p><p>Where do I put this?</p><p>Do I really have time to fill a whole form just to not forget one call?</p><p>Scopit was born from that tension: I wanted an interface where time becomes readable again, without turning my day into a wall of forms and micro-decisions.</p><p>With version 1.3, the Today inbox in Scopit gets two upgrades that go exactly in that direction:</p><p>•	a new Quick Add field that understands short, natural sentences,</p><p>•	long-press actions on events that reduce friction when you’re in execution mode.</p><p>This post is a quick tour of what changed and, more importantly, why.</p><p>⸻</p><p>The Today inbox as a control tower</p><p>In Scopit, the Today tab isn’t just “another list” – it’s meant to be your control tower:</p><p>•	Today’s events you actually want to move forward.</p><p>•	Overdue items that still matter and need to be seen.</p><p>•	Undated things that you want to keep in play without assigning a deadline.</p><p>•	Recently completed events, so you can see what actually happened.</p><p>The philosophy is simple:</p><p>Don’t hide reality behind gamification.</p><p>Show what’s on your plate, but keep it readable and manageable.</p><p>Until now, capturing a new event in that system meant opening the add sheet, filling in fields, picking a date, maybe a time, maybe a tag… It worked, but it was too “form-like” for quick capture.</p><p>That’s where Quick Add comes in.</p><p>⸻</p><p>Quick Add: type like you think</p><p>At the top of the Today inbox, you’ll now see a simple field:</p><p>“Quick Add…”</p><p>You can still type a plain title if you want:</p><p>•	Call Alex</p><p>•	Book dentist</p><p>But Quick Add becomes really useful when you let yourself write like you naturally think about the event:</p><p>•	Tomorrow 9:00 call Alex #work</p><p>•	Fri 18:30 dinner with Sarah #friends</p><p>•	Pay rent on the 5th ! #money</p><p>From that single line, Scopit will:</p><p>•	Set the date (Today, Tomorrow, a weekday, or an explicit day like 15/02 or 2025–02–15).</p><p>•	Set the time if you include one (9:00, 21h, etc.).</p><p>•	Turn hashtags into tags, so #work or #friends become first-class tags in your system.</p><p>•	Adjust priority when you use exclamation marks:</p><p>•	! for important</p><p>•	!! for urgent</p><p>You don’t have to learn a “programming language” for your tasks. The parser is intentionally light and forgiving:</p><p>•	If it can’t find a date, the event lands in Today (that’s where you are, after all).</p><p>•	If it can’t parse a time, the event is created as an all-day entry for that date.</p><p>•	If it sees something that looks like https://…, it’s kept as a link on the event.</p><p>Quick Add is not meant to replace the full editor. It’s the shortcut you use when an idea pops and you want it safely out of your head in one sentence.</p><p>⸻</p><p>Long-press actions: when you’re executing, not planning</p><p>The other big change in this release is how you interact with existing events.</p><p>Previously, if you wanted to:</p><p>•	quickly edit an event,</p><p>•	copy a deep link to it,</p><p>•	or do a small operation without leaving the list,</p><p>you had to rely on swipes, taps, and sometimes dig back into the editor.</p><p>Now, you can simply long-press any event row (almost anywhere in the app’s list views):</p><p>•	In Today:</p><p>•	Today, Overdue, Undated, and recently Completed sections.</p><p>•	In Upcoming and Past:</p><p>•	all grouped sections (weeks / months / years).</p><p>A single long press opens a context menu with:</p><p>•	Edit event… (first item)</p><p>•	Copy UUID (for debugging, automation or support)</p><p>•	Copy deep link (e.g. scopit://event/&lt;UUID&gt;)</p><p>•	Open deep link (to test or trigger your own x-callback workflows)</p><p>Imported Calendar events also get a context menu with debug options, but remain read-only from Scopit’s side – you still manage them in the system Calendar app.</p><p>The goal here is not to expose every possible action in a menu. It’s to make the frequent operations:</p><p>•	“let me adjust this quickly”,</p><p>•	“I want this link in another note”,</p><p>•	“I need a stable ID for this event”,</p><p>feel one gesture away, without breaking your reading flow.</p><p>⸻</p><p>Calendar &amp; Forecast: small fixes that matter over time</p><p>Alongside these new interactions, this update also fixes two behaviours that could create friction in daily use:</p><p>1.	Calendar events are now correctly sorted by time, not just by date.</p><p>If you import events from your calendars, they’ll appear in chronological order within the day – as you’d naturally expect when scanning your Today view.</p><p>2.	The Forecast section at the top of Today now uses unique calendar events and counts them correctly:</p><p>•	No more double counting,</p><p>•	Totals for Today / Overdue / Undated are consistent with what you actually see in the list.</p><p>Individually, these are small adjustments. Over weeks and months, they directly impact how trustworthy your inbox feels. And trust is everything in a system like this.</p><p>⸻</p><p>Why I’m leaning into natural capture (even without full AI yet)</p><p>There’s a lot of talk around AI, smart assistants, and fully automated planning. Scopit will definitely grow in that direction – especially around:</p><p>•	smarter reviews,</p><p>•	better suggestions for what to do next,</p><p>•	surfacing “sleeping” notes and commitments.</p><p>But I wanted Quick Add to be:</p><p>•	local (no account, no server round-trip needed),</p><p>•	predictable (you can see exactly what it did from your sentence),</p><p>•	and fast (type, hit return, done).</p><p>It’s a first step towards a richer language for your events. Even without a big AI model in the loop, you already get a lot of value from:</p><p>•	dates,</p><p>•	times,</p><p>•	tags,</p><p>•	and priorities,</p><p>decoded from one short sentence.</p><p>The idea is simple:</p><p>capture should be lighter than the thought you’re trying not to lose.</p><p>⸻</p><p>What’s next</p><p>Now that the Today inbox has:</p><p>•	a Quick Add to capture,</p><p>•	long-press shortcuts to adjust things in place,</p><p>•	and a cleaner integration with Calendar and Forecast,</p><p>the next natural areas to improve are:</p><p>•	more flexible natural language (recurring events, domains, etc.),</p><p>•	a smarter review layer that helps you revisit what matters at the right time,</p><p>•	and eventually, AI-powered insights that stay aligned with Scopit’s core philosophy:</p><p>help you see time clearly, not game it.</p><p>If you’re already using Scopit, I’d love to hear how the new Quick Add fits into your day.</p><p>If you’re discovering it with this post: the app is available on iOS, no account required, with a small free tier so you can test the flow in your real life.</p><p>Thanks for reading – and enjoy a faster Today inbox.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*Fchl9OWI7bxGyNkHzaHupA@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=651efca26488" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Most Task Systems Die After 3 Weeks (And How to Build a Living One)]]></title>
            <link>https://medium.com/@lbezeaud/why-most-task-systems-die-after-3-weeks-and-how-to-build-a-living-one-9c1c66d39126?source=rss-c4ce46cdce6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c1c66d39126</guid>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Claude Bezeaud]]></dc:creator>
            <pubDate>Mon, 01 Dec 2025 07:30:17 GMT</pubDate>
            <atom:updated>2025-12-01T08:03:05.137Z</atom:updated>
            <content:encoded><![CDATA[<p>We’ve all done it.</p><p>New app, new notebook, new system.</p><p>You spend an evening setting everything up: projects, tags, deadlines, colors.</p><p>For a moment, it feels like this is it. This time, you’re going to be on top of everything.</p><p>Fast-forward three weeks.</p><p>Notifications are piling up.</p><p>You swipe a few away “for later”.</p><p>You start ignoring the badge count.</p><p>At some point, you stop opening the app entirely.</p><p>The system didn’t explode dramatically.</p><p>It just… quietly died.</p><p>Why does this happen so often? And more importantly: what would it take to build a system that actually stays alive?</p><p>In this article, I want to explore that question and share a different way of thinking about tasks: not as static to-dos, but as part of a living system that evolves with your time, your attention, and your reality.</p><p>⸻</p><p>The Short, Tragic Life of a Typical Task System</p><p>Most task systems follow the same three-act script.</p><p>Act 1 – The Honeymoon</p><p>You set everything up from scratch:</p><p>•	You import old reminders from your phone.</p><p>•	You create projects for work, personal life, health, side projects.</p><p>•	You assign deadlines to almost everything “to stay accountable”.</p><p>•	You add tags, priorities, maybe even estimates.</p><p>It feels great.</p><p>You’re not just organizing tasks; you’re designing a better version of yourself.</p><p>For a while, you keep up:</p><p>•	You check your list in the morning.</p><p>•	You tick off a few things every day.</p><p>•	You feel a hit of satisfaction every time something gets marked as done.</p><p>So far so good.</p><p>Act 2 – The Slow Drift</p><p>Then, reality kicks in.</p><p>Meetings move. Emergencies appear. Priorities shift.</p><p>You postpone a task once… twice… five times.</p><p>A few things happen in the background:</p><p>•	Some tasks are no longer relevant, but they’re still in your system.</p><p>•	New tasks arrive faster than you can re-organize.</p><p>•	Old tasks sink lower and lower, but they still carry a little guilt every time you scroll past them.</p><p>You start to feel something subtle but dangerous:</p><p>“This list doesn’t quite reflect my real life anymore.”</p><p>That’s the moment the system starts drifting away from reality.</p><p>Act 3 – Quiet Abandonment</p><p>At some point, you stop trusting the list.</p><p>When a reminder pops up, you don’t think:</p><p>“Oh good, this helps me.”</p><p>You think:</p><p>“Ugh, not now. Dismiss.”</p><p>Two common reactions appear:</p><p>•	You check tasks off just to clear the notification, even if the work isn’t done.</p><p>•	Or you ignore the app entirely, mentally marking it as “broken” or “overwhelming”.</p><p>The system isn’t helping you make sense of your time anymore.</p><p>It has become noise.</p><p>And from there, the ending is predictable:</p><p>you abandon it and wait a few months until the next app or method promises a fresh start.</p><p>⸻</p><p>The Hidden Killer: Static Systems in a Moving Life</p><p>The core problem isn’t that you’re lazy, or disorganized, or “bad at sticking to systems”.</p><p>The problem is that most task systems are designed as if time were static.</p><p>You’re asked to:</p><p>•	Set a due date.</p><p>•	Place the task in a project.</p><p>•	Maybe add a priority or a tag.</p><p>And then… that’s it.</p><p>From the system’s perspective, the task is now “defined”.</p><p>But your life isn’t.</p><p>Your week changes. Your energy fluctuates. New constraints appear.</p><p>Yet many systems behave as if the plan you made on Day 1 should remain valid forever.</p><p>Over time, this creates a gap:</p><p>•	On one side: your lived reality</p><p>•	On the other: the frozen snapshot of your intentions from when you created the task</p><p>The bigger the gap, the less you trust the system.</p><p>When people say “my setup stopped working”, they often mean:</p><p>“My life changed, and my system didn’t come with me.”</p><p>⸻</p><p>What a “Living System” Looks Like</p><p>So what’s the alternative?</p><p>Instead of treating your task list as a stone tablet, think of it as a living system – something that:</p><p>•	reacts to changes,</p><p>•	invites regular interaction,</p><p>•	and stays aligned with what actually matters now.</p><p>Here are some characteristics of a living system.</p><ol><li>It’s Built Around Time, Not Just Lists</li></ol><p>A living system doesn’t just ask “What?”</p><p>It constantly cares about “When?”</p><p>•	Is this for today, this week, later, or someday?</p><p>•	Is this time-sensitive (a real deadline) or just aspirational?</p><p>•	Has this been sitting untouched for weeks? If yes, why?</p><p>Tasks aren’t just items; they are events in time.</p><p>A living system reflects that: it helps you see what’s near, what’s far, and what’s already behind you.</p><p>2. It Encourages Regular Re-Decision</p><p>Creating a task is not a final decision.</p><p>It’s a proposal.</p><p>A living system understands that you will need to:</p><p>•	renegotiate deadlines</p><p>•	reclassify priorities</p><p>•	abandon certain tasks entirely</p><p>Instead of quietly accumulating old commitments, it asks:</p><p>•	“Does this still matter?”</p><p>•	“Is this still the right moment?”</p><p>•	“Do you still want to carry this?”</p><p>Sometimes, the healthiest action is not to do the task – it’s to let it go.</p><p>3. It Makes Status Changes Easy (and Meaningful)</p><p>In a dead system, only two states really exist:</p><p>•	not done</p><p>•	done</p><p>In a living system, there are more organic states:</p><p>•	planned</p><p>•	in progress</p><p>•	on hold</p><p>•	waiting for someone else</p><p>•	moved to later</p><p>•	no longer relevant</p><p>The more naturally you can move tasks between these states, the more your system reflects reality instead of an idealized plan.</p><p>4. It Helps You See Progress, Not Just Load</p><p>A good living system gives you a sense of movement:</p><p>•	what you’ve carried from week to week,</p><p>•	what you’ve actually done,</p><p>•	what has gently fallen off the map.</p><p>If all you ever see is “what’s left”, you will eventually feel crushed.</p><p>If you occasionally see “what has already moved”, your system becomes a mirror of your efforts, not just your obligations.</p><p>⸻</p><p>A Simple Weekly Ritual to Keep Your System Alive</p><p>You don’t need a complex framework to have a living system.</p><p>You mainly need a consistent, lightweight ritual.</p><p>Here’s one you can start with:</p><p>20 – 30 minutes, once a week.</p><p>You can call it a “review”, but I prefer to see it as a moment of alignment.</p><p>Step 1 – Look at the Past Week</p><p>Open your system and focus only on the last 7 days:</p><p>•	What did you actually complete?</p><p>•	Which events or tasks turned out to be more important than you expected?</p><p>•	Which ones were postponed, and why?</p><p>Don’t judge. Don’t optimize yet.</p><p>Just observe.</p><p>This gives you a realistic picture of how your time was truly spent – not how you planned to spend it.</p><p>Step 2 – Gently Clean the Dead Weight</p><p>Now look at everything that:</p><p>•	has been postponed several times, or</p><p>•	has been sitting in your list for weeks with no movement.</p><p>For each of those, ask:</p><p>•	“Is this still relevant?”</p><p>•	“Do I really intend to do this?”</p><p>•	“If I had to do it this week, would I still say yes?”</p><p>Then take one of these actions:</p><p>•	Keep &amp; recommit → give it a fresh placement in time (this week, next, later).</p><p>•	Transform → split it into smaller pieces, or turn it into a simpler next step.</p><p>•	Let it go → delete or archive.</p><p>Every time you delete something that no longer matters, your system becomes lighter and more trustworthy.</p><p>Step 3 – Re-anchor the Coming Week</p><p>Now turn to the next 7 days.</p><p>•	Which tasks truly belong to this week?</p><p>•	Which ones are realistically for later?</p><p>•	Are there 1 – 3 key outcomes you want to focus on?</p><p>The idea isn’t to fill every slot with tasks.</p><p>It’s to ensure that what you see for the coming days matches your actual capacity and priorities.</p><p>If you look at your list for tomorrow and instinctively think, “No way”, you’re not done yet.</p><p>Step 4 – Close With One Small Adjustment</p><p>Before you end the ritual, pick one small change that will make your system feel more humane:</p><p>•	Reduce the number of daily notifications.</p><p>•	Rename a project to better reflect what it really is.</p><p>•	Add a tag that helps you spot “small, easy wins” for low-energy moments.</p><p>•	Or simply archive a project that no longer deserves your attention.</p><p>That small adjustment is a signal to yourself:</p><p>“This system is allowed to evolve. It moves with me.”</p><p>⸻</p><p>Your System Is a Conversation, Not a Contract</p><p>The big mindset shift is this:</p><p>Your task system is not a contract you must obey.</p><p>It’s a conversation between you and your time.</p><p>When that conversation stops, your system dies.</p><p>Instead of trying to build the “perfect” setup once and for all, aim for something more modest and more powerful:</p><p>•	A system that you touch often.</p><p>•	A system that reflects your current reality, not last month’s ambitions.</p><p>•	A system that makes it feel natural to say:</p><p>•	“This still matters.”</p><p>•	“This can wait.”</p><p>•	“This no longer belongs here.”</p><p>That’s what I mean by a living system.</p><p>⸻</p><p>A Personal Note</p><p>I’m not writing this from a perfectly organized mountaintop.</p><p>I’ve gone through the whole cycle myself:</p><p>new app, new structure, three intense weeks… then abandonment.</p><p>Many times.</p><p>That frustration is what pushed me to rethink how tasks and time could be handled, and eventually to start designing a tool around this idea of temporal clarity and living events, rather than static lists.</p><p>If this way of thinking resonates with you, you might like what I’m building with Scopit, an app focused on making your time feel readable, lighter, and more honest with how life actually moves.</p><p>You can take a look here: 👉 https://apps.apple.com/fr/app/scopit/id6752564453</p><p>But even without changing tools, you can start today with one simple step:</p><p>•	Give your system 20 minutes this week.</p><p>•	Clean what’s dead, recommit to what matters, and let the rest go.</p><p>That’s how a dead list becomes a living system again.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c1c66d39126" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>