Common foundation
Cross-checked inventory of your activity
Every two months, cross-check skills, dashboard, files and conversations to spot what is dormant, what diverges and what is missing.
The problem
A system that has been running for months drifts silently: a page is no longer refreshed, an event is missing from the dashboard, a date differs between the calendar and a record, an important file has never left Downloads, a scheduled task has remained paused.
Step-by-step method
- Cross-check four sources: the skills (what is planned), the dashboard (what is tracked), the files (what exists) and the conversations (what has been done).
- Inventory by domain: for each building block, its actual use over the period (used, never used, recently created).
- Status tables by domain: manuscripts, thesis defenses, studies, conferences, department, career, teaching; each row with the known status and the next step.
- List of inconsistencies:
- frozen data (a page that still cites an old version);
- events missing from the dashboard;
- conflicting dates between two sources;
- files not filed or not replicated;
- scheduled tasks whose active or paused state is unknown.
- Declare the source limits: what the AI cannot access (some projects, some sessions) is reconstructed from traces, and it says so.
- Correct: each inconsistency becomes an action to approve; the AI also corrects its own errors from the previous inventory.
Deliverable
A dated inventory, by domain, with the list of inconsistencies and actions. It is also the raw material for the annual activity report.
Safeguards
Consulting and finances are outside the scope of the academic inventory. No correction is applied without approval.
Starter prompt
Take an inventory of my academic activity over the last two months by cross-checking my skills, my dashboard, my files and our conversations. By domain: actual use of the building blocks, status of each file, next step. End with the list of inconsistencies and source limits.