<aside> 🧭

Northstar: Build small. Compose big.

Create small, composable, reusable Data Jar utilities with clear inputs and outputs, then combine them into larger automations.

</aside>

Project Purpose

Build a reusable Data Jar Toolkit for Oneseco Media made from atomic Shortcuts and utilities. The toolkit should support file organization, automation state, counters, logs, configuration, and future agent workflows without turning into one giant Shortcut.

Core Architecture

Data Jar stores state. Atomic utilities manipulate state. Orchestrators decide when those utilities run.

• Data Jar → persistent local state
• Atomic Shortcuts → one deterministic operation each
• Orchestrator Shortcut → chains utilities into workflows
• Agents → decide what should happen when reasoning is needed
• Pushcut → triggers and notifications
• Cloudflare Workers → remote APIs and network execution

Data Jar Root Dictionary

DJToolkit

Suggested structure:

DJToolkit
├── config
├── counters
├── fileRules
├── logs
└── state

First Atomic Utilities

• [ ] DJ Get — Input: key → Output: value
• [ ] DJ Set — Input: key + value → Output: saved value
• [ ] DJ Exists — Input: key → Output: true/false
• [ ] DJ Ensure Default — Input: key + default → Output: guaranteed value