Tasks
via Dida365
task.listtask.createREADWRITE LOW
OPEN SOURCE · SELF-HOSTED
$ tar what-makes-you-tick
Your digital world, gathered.
MODEL AGNOSTIC·PRIVATE BY DEFAULT·OPEN BY DESIGN
ASK TICK TAR
One question. The right tools.
It translates intent into approved capabilities.
It never hands
your secrets to an AI.
Ask Tick Tar
DEMO
Your day, gathered.
You have 3 tasks and 2 calendar events remaining today.
CAPABILITIES
task.listcalendar.list
CONNECTED PROVIDERSDida365CalDAV
Read-only request · no confirmation needed
YOUR CAPABILITIES
Tools AI can use.
Only when you allow.
Capabilities stay stable. Providers can change.
Permissions
belong to each action.
Calendar
via CalDAV
calendar.listcalendar.createREADWRITE LOW
Music
via QQ Music
music.currentmusic.recentREAD
Code
via GitHub
github.issue.createEXTERNAL
Files
via Synology
file.searchfile.getSENSITIVE
Home
No provider connected
home.light.setWRITE HIGH
Example capabilities and provider status. No providers are connected in this demo.
CONNECTIONS
Bring your own services.
Connections configure a provider.
They do not grant AI or
public access.
TASKS
Default provider
✓
Dida365Task capability · Demo connection
Connected
FILES
Available sources
▤
Synology NASFile capability · Demo connection
Connected
THREE SEPARATE BOUNDARIES
01Connection
Provider credential stored by Tick Tar.
02AI permission
Action-level allow, ask, or deny.
03Public visibility
Only explicitly published data appears here.
PUBLIC PAGE · A TICK TAR VIEW
A window into what you choose to share.
Projects, notes, and moments can live here.
Tasks, files,
devices, and memory stay private by default.
kim.ticktar.homeDEMO
Public view · Explicitly
shared
Make it your own. Use the arrows to move a widget. This demo keeps your layout for this visit.
PRIVATE BY DEFAULT
Publish explicitly. Act with permission.
Who asked. What ran. Which provider answered.
Sensitive values
are summarized, never logged as secrets.
DEMO DATA
Recent actions
Policy is evaluated before a provider is called.
READWRITE LOWASK
-
✓
AI created taskCONFIRMED
task.create· via Dida365 · “Review design proposal” -
▦
AI read calendarREAD
calendar.list· via CalDAV · 2 events returned -
▤
AI searched filesSENSITIVE
file.search· via Synology · sensitive paths redacted
CANONICAL HISTORY
Sources change.
Your history stays.
Providers can come and go.
Your timeline remains continuous.
QQ MusicNetEaseOther
→
NORMALIZEMusic
→
music.listen.v1
Continuous timeline
Architecture example · sample providers · no live accounts
YOUR DIGITAL TIMELINE
The days add up to you.
Not everything needs its own tab.
Follow the threads of your
digital life.
SEP 28Monday
Code
A little more life in Homestead
3 commits · Sensor cards, softer transitions, a better morning view.
Note
A home on the internet, not another feed.
Published to Fieldnotes · 3 min read
Music
A slow start, a familiar soundtrack.
Weightless — Marconi Union
SEP 27Sunday
Photos
Salt air and a little perspective.
12 new photos · Weekend fragments
Bookmark
Four ideas worth coming back to.
Saved to Reading corner · Design, local-first, and slower software.
NO WALLED GARDENS
Everything
stays yours.
Your space shouldn't depend on someone else's platform.
Run it
on your terms. Take it with you.
01
Self-hosted
At home on your own infrastructure.
02
Open source
Understand it. Change it. Make it better.
03
Portable
A digital home designed to move with you.
04
Exportable
Your memories deserve an open door.
05
Permission controlled
Every action has an explicit boundary.
06
Auditable
Actions leave a redacted, structured trace.
Product principles. Data export and integrations are planned.
BUILT IN THE OPEN
Tick Tar Open source
Canonical personal data and capability layer
—Stars
—Forks
—Contributors
—Latest release
Deploy it on your infrastructure. Your database and credentials stay with your instance. Repository links are configuration-driven and will appear when published.