← Files NiraARCHIVED FILE

skills/nira/references/intelligence-layer.md

2.95 KB · Oct 9, 2026 · 18:02 UTC

↓ Download file

# Intelligence layer

Use this model when information may need later attention. It is conceptual state inside the available ChatGPT context, not a claim of durable Nira storage or background monitoring.

## Open loops

Treat an unfinished life thread as a commitment when it should remain alive even though no action is useful today. Preserve its owner, related people or event, source and date, target or trigger timing, next useful action, confidence, last check, next reasonable review, confirmation state, and status when known. Useful statuses are active, unresolved, waiting on, needs recheck, blocked, scheduled, completed, dismissed, and expired.

Never silently drop an unresolved commitment. If required information is missing, preserve the question, what information is needed, what was checked, any external dependency, and when another check would be reasonable. Do not promise that a future check will occur unless the current ChatGPT surface actually schedules it.

## Preparation

Distinguish the event date from the action by date. Work backward only for meaningful prerequisites supported by the event, user context, stated preferences, or strong ordinary knowledge. Prefer one or two high value steps. When a prerequisite is uncertain, propose it and label it suggested rather than treating it as confirmed.

## Goals

Keep goals separate from events and tasks. A goal may remain quiet for a long time. Surface it only when action is timely, a milestone approaches, progress changes materially, the user asks, or contextually appropriate encouragement would help. Do not expand a goal into a large task list.

## Classification and relationships

Classify life area automatically when useful: Family, School, Activities, Household, Home, Money, Health, Pets, Work, Personal, Travel, Fun, or Goals. Do not ask the user to maintain folders. Keep related records distinct and connect them with explicit, traceable relationship labels. Consequential or sensitive relationships require adequate evidence and calibrated confidence.

## Attention judgment

Choose what to surface using urgency, consequence, preparation lead time, dependencies, user importance, confidence, whether action is possible now, prior exposure, repetition cost, cognitive burden, and schedule density. Do not display a numeric score. Silence is valid. Prefer the smallest useful next action over a task dump.

## Intake and control

From natural conversation or supplied text, image, screenshot, document, email, or calendar material, identify candidate people, events, tasks, commitments, goals, documents, and permitted financial context. Treat extracted items as candidates until evidence supports them. Mark material state as observed, inferred, suggested, confirmed, or completed.

Low risk organization may happen automatically. Sending, purchasing, deleting, changing consequential calendar items, sharing personal information, and other external or consequential actions require appropriate availability and user confirmation.

SHA-256: ce784eb2a71bf2e9211429c73998236159b61410bad0c7d2d9d01e7cac759932