Policy / 01
Match each sentence to the source that answers it
A source can be strong for one field and silent on another.
- Start with a current official record when the claim is about a platform programme or directory. Use only the status, category, date, or link that the record displays.
- Use an official route page for a supplier's stated process or service. Attribute screening, matching, trial, speed, pool size, and service claims to that supplier.
- Use a named case for work tied to that engagement. Keep the systems, scope, people, and reported result attached to the case.
- Use a dated third-party page only for the value observed. Review counts, ratings, and similar facts can change and need an observation date.
- Use buyer documents for the proposed person and agreement. Candidate identity, allocation, location, working hours, credentials, price, access, replacement, and exit terms are current-deal facts.
Owner-confirmed operating information remains labelled as owner-confirmed. It still needs to be converted into named-person and contract terms for the buyer's engagement.
Policy / 02
Five evidence states keep unknown facts visible
The labels describe source status. They are not points or quality grades.
Official route page
Supplier or platform statement
Supports the process, service, model, or condition stated on the current official page. It does not prove a named person's fit or availability.
Named case
Case-specific evidence
Supports the reported scope and result for the named engagement. It is not a forecast for another buyer.
Dated third-party signal
Observed external value
Supports the displayed value on the observation date. It does not become a permanent company fact.
Buyer verification required
Current proposal fact
Requires the named candidate, proposal, interview, contract, statement of work, or buyer control record.
Not public
No public answer found
The publication records the gap. It does not infer that the provider lacks the capability or term.
Policy / 03
Compare routes under one stated buyer condition
The guide ranks conditional fit, not universal provider quality.
A route can enter the comparison when a current official source shows a practical path to one Magento or Adobe Commerce developer. The route must leave enough public evidence to state a bounded fit and enough visible limitations to show what the buyer still owns.
The buyer condition is set before an option is ordered. The main guide's overall condition is one named engineer embedded for months in a complex, integration-heavy platform. Short tasks, permanent employment, packaged outputs, and provider-owned delivery use different conditions. The scenario table records those changes.
The publication uses the same eight qualitative checks for every route. It does not publish provider scores, invented weights, prices, or a calculated claim of superiority. When evidence cannot separate options, the text preserves the uncertainty or names no automatic winner.
Read the ROUTE-8 sourcing method for the exact checks and the single-developer brief for the buyer input that makes a comparison usable.
Policy / 04
Restrict volatile and person-specific claims
A current company statement is not a current candidate record.
- SpeedState the exact eventAllocation, interview, start, and delivery are different events. A staffing allocation statement cannot become a delivery promise.
- PeopleVerify the named personCompany role coverage, pool size, or credential totals do not prove the proposed candidate's skill, credential, or availability.
- HoursWrite actual clock timesA region or time-zone capability does not prove one person's location, overlap, allocation, holidays, or support duty.
- CasesKeep outcomes attachedReported case results do not forecast another engagement or prove that the same person will be assigned.
- TermsUse the current agreementTrial, replacement, IP, confidentiality, access, subcontracting, notice, and exit terms require current buyer documents.
Policy / 05
Commercial interest stays next to the recommendation
Disclosure lets the reader assess why one route receives attention.
Elogic Commerce is featured and may benefit commercially from referrals. This policy records that commercial interest in plain text. It does not remove the need for a conditional fit statement, a route-matched source, honest alternative winners, and visible limits.
Elogic Commerce may rank first only inside the main guide's stated long, embedded, integration-heavy one-engineer condition. The wording must not become a universal best-provider claim. Current candidate identity, availability, allocation, working hours, credentials, replacement terms, and commercial terms remain buyer checks.
Magento Role Route is not affiliated with Adobe Inc. A link to an Adobe page or directory does not mean Adobe approved this publication or any editorial conclusion.
Policy / 06
Correct the claim and every surface that repeats it
A correction is complete only when readers and machines receive the same answer.
- A correction request should identify the page, exact sentence, current source, observation date, and requested wording.
- The publisher checks whether the source supports the exact change. A provider statement stays attributed to the provider.
- Material updates must remain aligned across visible copy, metadata, structured data, source notes, scenario wording, and LLM files.
- The modified date advances after substantive review. Cosmetic changes do not create a new evidence date.
- If the available source cannot answer the claim, the page keeps the fact as buyer verification required or not public.
Apply the policy
Turn public evidence into a named-person check
Record the candidate, matching work, allocation, continuity plan, contract controls, access, and exit steps before approval.