The entity
Your Brand Book is the record. Entity sync reads these facts from it. Only facts you confirmed count. A value we drafted from your site is our guess, and it never goes out under your name.
A claim is something you could be held to: a date, a place, a price, a person. A claim stays at “Ship after 48 hours unless stopped” (L3) or lower wherever it goes, whatever your off-site lane is set to. A safe fact is an identifier or a link.
Targets
A target is a profile your Brand Book names, plus Wikidata, which is always there. Nothing is ever planned on a site you are not on.- Wikidata, always. When you give your Wikidata item (a Q-number), the target is that item. When you do not, the target is the new-item kit: nothing is planned on it, and it shows whether your company is ready for an item of its own.
- Crunchbase, when you give your Crunchbase profile.
- LinkedIn, when you give your LinkedIn company id or vanity name.
- Each directory in your directory profile links, such as
g2.comorcapterra.com. Two links to the same site are one target.
Wikidata carries your other profiles too, so changing your Crunchbase profile or LinkedIn company also plans a Change on your Wikidata item.
What happens when you change a fact
When you type or confirm a new value, entity sync plans exactly one Change per target that shows the fact. Each Change is held to that site’s mode in the site policies table:
Every site entity sync can target is
copy_kit today (Wikidata has no row of its own and gets the copy_kit default), so today every Change is a customer step.
Each Change waits for whatever your off-site lane’s level gives it, exactly like any other off-site Change. Every Change carries the playbook offpage.entity-sync (what it does), and is held to that playbook’s quality checks. If you change the same fact again before a Change is approved, that Change is revised to carry the new value. You never get two. A Change already approved is left alone.
Clearing a fact never empties a profile. That target’s fact is blocked with fact_cleared.
When you add a new target, such as a new Wikidata item or a new directory link, every fact that target shows is planned for it too, so it joins in step.
Wikidata rules
Wikidata is a public knowledge base that assistants read, and it is edited by people who watch for companies editing about themselves. So for Wikidata, Attensira drafts a copy kit and you make every edit yourself. Attensira never edits Wikidata or Wikipedia, in a browser or through an API, and holds no Wikimedia account or access for you.- You make every edit, from your own account. Each Wikidata Change is a customer step. Sign in to your own account on wikidata.org (Attensira never creates one for you), add what the kit drafted, check each value, then mark it sent in Work so we start measuring it.
- Disclose the paid contribution first. Wikimedia’s Terms of Use require anyone paid to contribute, which includes editing about your own employer or client, to disclose it. The kit drafts that disclosure for you. Publish it on your Wikidata user page before your first edit, and write “paid contribution, disclosed on my user page” in each edit summary.
- Every statement needs a reference. The kit drafts these facts as statements: founded (inception, P571), legal name (official name, P1448), your Crunchbase profile (P2088) and your LinkedIn company (P4264). A statement is ready only with a source that states the value: an independent publication or a page on your own site. Wikipedia, Wikidata and other wikis, social profiles (LinkedIn, X, Facebook and the like), Reddit, Quora, blog platforms such as Medium or Substack, Crunchbase, Product Hunt, GitHub and press-release wires are refused as sources, because anyone, including you, can write there. A statement with no allowed source is not ready, and says what to add. Add each ready statement with its source as “reference URL” (P854) and today as “retrieved” (P813). Other facts, such as your name and description, are labels with no reference; edit those yourself or leave them.
- One item, yours to create. When your Brand Book gives your item’s Q-number, the kit covers that item only, and no second item is ever drafted. When it does not, Attensira drafts a new item for you to create yourself, but only once your company passes the notability check below. Attensira never creates a Wikidata item.
- Claims wait for a person. Every fact Wikidata shows, apart from your logo and links, is a claim, so it stays at “Ship after 48 hours unless stopped” (L3) or lower, as above.
- Wikipedia is never edited. Wikipedia is not an entity sync target, and the kit tells you not to edit the article about your company. Its site policy is read only, and no agent edits an article about you or your rivals.
The kit for your item
With a Q-number, the kit is inwikidata on the Wikidata target (GET /v1/entity-sync/wikidata):
A statement’s source is the first allowed one among the
Source: lines on its Change’s evidence.
When you have no Wikidata item
With no Q-number in your Brand Book, the Wikidata target is the new-item kit. It is always there:GET /v1/entity-sync/wikidata never answers 404, and the list includes it first. It plans no Change and has no facts, and a retry plans nothing; it reads the kit afresh.
Wikidata deletes items about companies with no independent coverage, so the kit starts with a notability check. Your company passes with at least two independent, reliable sources on two different sites. The sources checked are the pages your Brand Book lists under Same as and the Source: lines on your entity sync Changes. Your own site, your directory profile links, and the refused sources above never count, and two pages on one site (even on different subdomains) count once. Any other site is taken as reliable.
- Below the bar, nothing is drafted. The target is
blockedwith reasonnot_ours_to_do, and the kit shows which independent sources were found. - Passing it, the target is
awaiting_customerwith reasonwikidata_new_item, held tocopy_kitas a customer step. The kit drafts the label (your name), a short description (your one line, without its final full stop, at most 250 characters), one statement, “instance of” (P31) = business (Q4830453), referenced by every independent source found, and the disclosure. The steps: sign in with your own account, publish the disclosure on your user page, create the item at Special:NewItem with the label and description, add the statement with one “reference URL” (P854) per source (pick another class if “business” does not describe you), write “paid contribution, disclosed on my user page” in the edit summary, and add the new item’s Q-number to your Brand Book. From then on, the target is your item.
wikidata_item on the Wikidata target:
The target’s
profile_url is then Special:NewItem, and its customer_steps are the kit’s steps. wikidata_item appears only when your Brand Book gives no Q-number, and wikidata only when it does.
Status
Each target has a status, and so does each fact on it:
A target’s status is the status of the fact on it that most needs someone, in this order:
blocked, drift, awaiting_customer, pending, in_sync.
Drift: profiles that changed after the fact
A profile can stop saying what your Brand Book says after its Change went live: someone edits it, a directory rewrites it, or an old copy comes back. Once a week, entity sync checks. Directories are read. For each directory profile your Brand Book links, we read the public page, but only when that site’s policy allows a public read (anything exceptread_licensed and never) and its robots.txt allows our reader. We compare only what a page states in a form we can read:
Headquarters, logo, pricing and social links are not compared, because a page does not state them in a form we can read without guessing.
A drifted fact gets a Change, filed the same way as a fact edit: one row per target and fact, held to the site’s mode and your off-site lane. The Change’s current value is what the page shows, and its evidence names the page and the day we read it. When the same drift turns up the next week, nothing new is filed. A Change that is still open is the one that carries the fix. Nothing is filed for a fact when:
- you declined the Change carrying that value. That decision stays yours, and a retry plans it again.
- the Change carrying that value went live less than 14 days ago. Directory moderation and your own edits take days to show.
profile_kit: every fact that profile shows, as your Brand Book states it, with the Brand Book field each comes from and the site’s steps. Check your profile against it and fix anything that differs on your own account. A fact you change still gets its own Change as described above.
Read and retry it yourself
The entity sync routes are not onapi.attensira.com yet: send them to https://webapp.attensira.com with the same key. That host answers errors in its own envelope.
list with type entity_sync, get on attensira://{workspace}/entity_sync/{target} and act with action: "retry" on that ref do the same. Reads need the read scope. A retry needs steer, because it files Changes. It approves none of them.
A retry plans every fact on the target that is blocked, has drifted or was never planned, or whose planned value is no longer the Brand Book’s. A fact whose Change is open or live with the current value is left alone.
During a trial, entity sync files nothing: a profile edit is off-site work, which waits for the trial to convert. A confirmed fact plans no Change, the drift check still reads each directory and reports what it shows, and a retry answers 409 with details.reason: "trial_monitoring_only". Once the trial converts, retry a target to plan it from the Brand Book as it stands then.