Use structured facts first
Category, deployment, integrations, pricing transparency, and capability fields are more useful than broad vendor positioning.
Portstack is useful only if buyers can see how information is sourced, where the gaps are, and how vendor influence is handled. The editorial model keeps the directory disciplined while it is still early.
The editorial standard is intentionally practical. It does not try to mimic a newsroom manual; it defines the guardrails that keep a product directory trustworthy.
Category, deployment, integrations, pricing transparency, and capability fields are more useful than broad vendor positioning.
Portstack does not publish universal winners, star ratings, or unverified superlatives.
Buyer communications should not become a hidden vendor channel without an explicit product decision.
Portstack should be easy to correct and hard to capture. A correction that points to a specific field and source is more useful than a rewrite request.
Missing products, outdated product names, wrong category placement, incorrect links, and better public sources.
Capability claims, customer signals, integrations, and deployment statements are checked against available evidence.
Requests to remove accurate but inconvenient information, hide uncertainty, or change comparison logic for positioning.
Sponsored placement may become a business model later, but it cannot change organic profile content, comparison rows, or whether a product belongs in a category.
Buyers should never have to infer whether a placement is commercial.
Vendors do not buy better capability values, hidden gaps, or different field models.
As volume grows, corrections should move from ad hoc intake to a clearer review workflow.
Correction path
Send the page, field, and source. Precise corrections are the fastest way to improve the directory.