Which Fields Sera Fills, and Which Are Yours

Which Fields Sera Fills, and Which Are Yours

An empty column is not automatically a fault. Every property in your hub belongs to one of four groups, and knowing which is the difference between "this is broken" and "this is waiting for me".

---

1. Sera fills these

The extraction layer. When Sera reads an email, a meeting transcript, or a document you share, she writes what the source actually says:

• Titles and summaries for every record she creates
• Owner and Assigned Role, when the source names a person or the role is inferable
• Priority and Status
• Due dates, but only when the source states an explicit deadline. An undated task is correct and expected: a guessed due date manufactures a false overdue list
• Relations to projects, circles, people and meetings, wherever she can resolve them
• Source Evidence, so every record can be traced back to what it came from
• Asserted By and Provenance Class, which record who stands behind a record and what kind of claim it is

2. Notion fills these

Automatic, and correctly untouched by anyone:

• Created time, Created by, Last edited time, Last edited by
• Unique IDs such as Policy ID, and formulas computed from them such as Policy Ref
• The far side of every relation. Link a task to a project and the project's task list updates itself

3. You fill these, and Sera deliberately never will

These are closure fields. They record a human judgment, and Sera writing one would be forging your decision:

| Field | Where | |---|---| | Resolution Notes, Resolved Date | Risks, Ledger entries, Tensions | | Rejection Reason | Memory Review, Canon Change Requests | | Completion Notes | Projects | | Implemented Date | Decisions | | Reviewed Date | Sensitive Review | | What Did Not Work | Retrospectives | | Attendance | Events |

If one of these is empty, it means nobody has closed that item yet. That is information, not a bug.

Confidential Identities belongs here too. That table is managed by an admin by hand, in a restricted space. Sera reads it so she can protect the identities inside, and never writes to it.

4. Currently filled by nobody

Honesty matters more than a clean sheet. These exist in the schema and nothing fills them today:

• Estimated Hours on Tasks
• Possible Duplicate Of on Knowledge Base
• Source Email ID and Meeting ID on Processing Events
• Google Drive Doc on Policies
• Acquisition Date, Last Inspected, Next Service Date on Resources
• Vital Sign, Unit, How to Measure on Vital Signs

You can fill any of them by hand and nothing will overwrite you. They are on the list to either wire up or remove, and they are named here rather than left for you to discover.

---

Why this article exists

An admin opened a table, saw a column of Empty, and reasonably concluded something was broken. Sometimes that is right and sometimes the column is waiting for a person. The only way to tell used to be asking us. Now it is written down.

If you find an empty column that is not on any list above, that IS worth flagging: it means the map is out of date, and the map is generated from the code, so a gap in it is a gap in our own picture.

Key points

Four groups. Sera fills the extraction fields: titles, summaries, owners, priorities, dates stated in the source, statuses, and every relation she can resolve. Notion fills the automatic ones: Created time, Created by, Last edited time, unique IDs like Policy ID, formulas like Policy Ref, and the far side of every relation. You fill the closure fields, and Sera deliberately never touches them: Resolution Notes, Resolved Date, Rejection Reason, Completion Notes, Implemented Date, Reviewed Date, What Did Not Work, Attendance. A judgment that something is resolved or rejected is a human act and Sera writing it would be forging your decision. A small number of fields are currently filled by nobody and are known gaps, listed below. The Confidential Identities table is deliberately human-managed and Sera reads it without ever writing to it.