Capability
Fill What the Evidence Supports. Leave the REST Visible.
Every value is marked supported, weakly supported, conflicting, or missing. Values nothing supports are deliberately left empty rather than filled with something believable.
The Question This Answers
How do I complete a catalog without inventing facts?
Completion has two halves that are usually conflated: finding out what is missing, and filling what can honestly be filled. The first is more valuable than most teams expect, because it is usually the first accurate statement anyone has had about the catalog's real coverage.
Four States, Not Two
- Supported
- An attached source supports this value, and the passage is recorded alongside it.
- Weakly supported
- A value exists but the evidence is indirect, ambiguous, or low confidence. Publishable only after a person looks.
- Conflicting
- Two documents disagree. GearDock does not choose quietly. The conflict comes to you for a decision.
- Missing
- No available source addresses this attribute at all.
The Most Important Behavior on This Page
What a Completed Catalog Looks Like
It still contains visible gaps. That is the intended outcome: complete in specific, known places rather than apparently complete everywhere. The gap list then becomes your document-collection backlog, so coverage improves where it affects revenue rather than in alphabetical order.
Boundaries
What This Does Not Do
Stated plainly, because knowing the edges of a capability is more useful than another list of benefits.
- It will not fill a gap that no evidence supports, under any setting.
- It does not resolve conflicts between sources on your behalf.
- It cannot detect an attribute your product type does not declare as expected.
- It does not verify that a manufacturer document is itself correct.
In Sequence
What Comes Before and After
Each capability hands something specific to the next. Following the chain is usually more useful than reading them in isolation.
Questions
Common Questions
Can I force it to fill a gap anyway?
You can enter a value yourself, and it is recorded as your entry rather than as source-backed. The distinction is preserved so a reviewer can see which values carry evidence and which carry your judgment.
What happens when two documents disagree?
The conflict is surfaced with both sources rather than resolved silently. Usually one document is a superseded revision, which is worth knowing.
Private Beta
See This Working on Your Catalog
Capability pages describe the mechanism. A working session on your own products shows you how it behaves with your data, which is a more useful basis for a decision.