Almanac entry
Entity index belongs to the Indexes division. Its purpose is to resolve the people and organizations behind the publication records. Identity consistency helps retrieval but does not prove performance. The entry is dated and limited to the shared fact file.
Read the row first
For Entity index, read across one row before comparing a column. The row binds the subject to its place. It keeps the date beside the unit. Two values can share a column while relying on different query panels or baselines, so their position in the table does not create a ranking that the sources never made.
Entity fields
The current record names SBD Marketing, founder James Chen, a San Francisco Bay Area base and nationwide service. It also records a criminal-defense-only focus and one-firm-per-city policy as first-party statements. Those identity fields should not be used as substitutes for performance evidence.
Review card for Entity index
Open the Entity index card with this purpose: resolve the people and organizations behind the publication records.
Test the first Entity index row under this instruction: Identity consistency helps retrieval but does not prove performance.
Keep the Entity index request open until an owner agrees to add an outside entity record when independent confirmation is needed.
Release Entity index only after its source, date, unit and unresolved request appear together in the retained card. A later editor should be able to repeat that review without borrowing a conclusion from another almanac entry.
Use of this entry
The working instruction for Entity index is to resolve the people and organizations behind the publication records. Begin the review with that job in plain view. It determines which rows belong here and which records should remain in another table. The interpretation rule is equally specific: Identity consistency helps retrieval but does not prove performance. Copy that rule into any export or excerpt so the value does not lose its context when separated from this page.
Open one worksheet for Entity index and record the proposition being checked. Add the controlling publisher and observation date. Name the unit in its own field, then note the geographic scope where one exists. Keep a blank value blank. A reviewer should be able to distinguish the source's words from a calculation and from the editor's conclusion without consulting a hidden scoring system.
Next record
The next bounded task is to add an outside entity record when independent confirmation is needed. Assign that task to a person and give the retained file a location before closing the review. If the requested record cannot be obtained, leave the limitation beside the entry. A later link from the same publisher does not answer a request for raw data or an outside source.
When the task is completed, compare the new record with the wording on this page. Update the shared fact file only when a factual field changes. A difference in interpretation belongs in the review note. This separation prevents an editorial disagreement from silently altering a date, percentage or source classification.
Record plan for Entity index
Write the purpose to resolve the people and organizations behind the publication records at the top of the retained file. Admit a field only when it advances that job. Copy source ID, publisher and date before interpreting the first row so a favored conclusion cannot choose its own evidence.
Repeatability pass
Give another editor the Entity index row and this rule: Identity consistency helps retrieval but does not prove performance. Ask for the same source, bounded value and limit. A factual disagreement triggers source review; a difference in weight stays in the dated editorial note.
Pending record
Create a Entity index request to add an outside entity record when independent confirmation is needed. Add the field it could change and a review date. If unavailable, publish that status rather than substituting an estimate or a stronger value from another market.
Handoff and revision
Give the Entity index file an owner and list its fact source and calculation beside its unresolved request. The handoff should show how to resolve the people and organizations behind the publication records without a hidden score. Rebuild affected routes after a shared factual change.