# Plan de acción — extended description

> Estructura tus tareas

Site: https://plan.ljg.cl
Version: 202611090250

## What it does

- Diagram of the plan: coloured columns (lines) with steps connected by tracks that never overlap; START at the top, the goal of every line at its end. A board view shows the same plan as columns of cards.
- Tabs group lines by topic (a line can be in several tabs; the main tab shows them all). Dependencies between tabs are marked and jump to the other tab.
- Priorities per line: high, normal, secondary or optional.
- Every user has their own plan. The administrator (defined in the server settings) manages accounts: requests from the registration form, approval, freezing, deletion, an activity log, a table of IP addresses and database trimming. It has no plan.
- Editing on the site: a wizard to add lines and steps; connections (requirements, decisions with options, suggested order, shared lines); dates (fixed, relative to other steps, soft and hard deadlines, waits, expected answers); files (photos, PDF, Markdown, text) with thumbnails and viewers. The server checks every change and must confirm it in time, or nothing is saved: circular dependencies and contradictory dates are rejected with the exact reason; deadlines that may be missed are accepted with a warning.
- Upload and download of a YAML file (the whole plan, or only some lines): the file is cleaned, checked strictly (English keys) and summarized before it is applied; the previous plan is kept as a backup.
- Countdowns (days, hours and minutes) to the start and the end of every step; when 48 hours pass after the date of a step without checking it, it fails together with what depends on it, and checking it later reopens the line after a confirmation.
- Collapse, archive, cancel and delete lines; after completing a line the app offers to archive it.
- Calendar: month, week and list on large screens; a week strip with a list on phones.
- Push notifications before every important date; several devices of the same user stay in sync.
- Works offline (installable PWA); light and dark themes that follow the device.

## The tasks.yaml file (format 5, English keys)

```yaml
format: 5
plan:
  title: "Moving house"
  start: 2027-03-01
tabs:
  - { id: HOME, name: "Home", icon: house }
lines:
  - id: FLAT
    name: "Find a flat"
    goal: FLAT_SIGNED
    priority: high
    tabs: [HOME]
    steps:
      - { id: FLAT_SEARCH, title: "Search listings", state: pending }
      - { id: FLAT_VISIT, title: "Visit flats", requires: FLAT_SEARCH, state: pending }
      - { id: FLAT_SIGNED, type: milestone, title: "Lease signed", requires: FLAT_VISIT, deadline: 2027-04-15 }
```

- Steps: id (UPPER_CASE key with the prefix of its line), title, type (task, wait, decision, milestone, document, uncertainty, note, junction), requires (expression: «A and (B or C="Yes")»), dates (date, not_before, due, deadline, auto_complete, expected, duration, validity), state (done, pending, or the choice of a decision), options (decisions), repeat, restarts, links, contacts, address, tags.
- Lines: id (2 to 6 uppercase letters or digits), name, goal (a step of the line), priority, tabs, steps; archived and cancelled are kept.
- Identifiers: the app keeps a uid of 64 characters [A-Za-z0-9] for every plan, tab, line and step. Keep existing uids when editing a file; new elements may omit them.
- Keys and fixed values are always English; texts may be in any language.

## Privacy

Plans, progress and files are private to each account. Nothing is shared with third parties.