Trust

Nothing here is trusted yet.

getedge asserts no Trust state over any skill in this private preview. No item is Signed, Tested, Evaluated or Recommended, no publisher is a Verified Publisher, and every skill page says so in those words rather than leaving the question open.

The three skills listed here were redistributed from one public repository at one pinned revision, under the Apache-2.0 licence that repository carries. Each was put through a single offline conformance check, run with no network access, which licensed exactly one claim: a deterministic offline static planning or composition artifact passed the candidate-specific conformance contract. No complete upstream workflow was executed. Nothing was measured about how well any of them works.

What is shown instead.

Every skill page carries the source it came from, the exact revision, the date that source was observed, the permissions its release declares, and the statement that no Trust assertion is attached. Those are records, not endorsements, and each one is read from the recorded source rather than written by hand.

Missing stays missing.

Where there is no assertion and no published compatibility claim, the catalog says there is none. It does not turn an absence into a badge, and it does not name an agent it has not tested behaviour on. Passive file transport was checked on five agents; behavioural compatibility is unverified on all five.

When public Trust assertions do exist, they will show their issuer, their subject, their date and their explanation on the page of the thing they are about. None exists today.