inspect Consumer Artifact(package: Lispex Package, bytes: Bytes, limits: Lispex Host Limits) - > Result<Lispex Consumer Artifact Inspection, Lispex Evidence Error>- 수신자
- 해당 없음
- 최소 인자 수
- 3
- 최대 인자 수
- 3
Declaration and parameters
링크사용 조건
기본 포함 · 아니요
Import std.lispex from an application package with a verified lock. Packages with [lispex] require --locked. Application profile topaz/ uses evaluator profile lispex/. Application profile topaz/ uses evaluator profile lispex/.
The generated-module resolver gate starts at language mode 5.18. Compatibility of this API with earlier released editions remains Pending. Target deployment conditions are native (native-only), web (web-isolated-workers), web- (web-isolated-workers). Runtime payload follows checker-reached rules. An empty reached-rule set includes no runtime payload. Application quotas are required. Lock-only packages do not receive these application modules.
수신자
매개변수 제약
inspectConsumerArtifact accepts an admitted package, complete artifact bytes and finite host limits. It decodes and validates the receipt and evidence bindings before returning an inspection.
Inspection performs no guest evaluation or replay. Structural validity does not authenticate an issuer. authenticateEvidence applies explicit trust separately.
std.lispex exports neither verifyConsumerArtifact nor consumerArtifactFromBytes. inspectConsumerArtifact is the single artifact byte admission operation.
관련 규칙 · Inspect and validate consumer artifacts in one call →inspectConsumerArtifact accepts an admitted package, complete supplied bytes and finite host limits. Validate the limits before decoding. Parse one complete artifact under its declared supported 2.0 container and codec versions.
Validate structure, integrity and supported semantic contracts. A portable receipt is required. Check that its complete request identity and canonical outcome agree with any included execution evidence and profile work binding. Reject trailing bytes, missing cores, inconsistent identities and unsupported versions.
Return an inspection containing the admitted immutable artifact, its LispexReceipt and optional LispexExecutionEvidence. artifactBytes is the byte count of the entire accepted representation. portableCoreBytes is the byte count of its portable receipt representation.
A missing execution evidence envelope is None. A validated signature envelope remains unauthenticated until authenticateEvidence accepts it under explicit trust. Structural inspection never sets an authenticated Boolean.
Invalid structure, missing portable receipt or inconsistent binding returns InvalidConsumerArtifact. Unsupported contracts or components return Admission. Exhausted host work, allocation, frame or channel budgets return LimitExceeded. The first failed check is retained without exposing a partially accepted artifact.
Inspection neither invokes the guest nor recreates a canonical outcome. It checks supplied records and cannot prove that a particular engine ran the program. Reproducing the recorded request is freshReplay and authenticating the issuer is authenticateEvidence.
consumerArtifactBytes returns the exact immutable accepted or produced container. portableCoreBytes returns its portable receipt bytes. Both representations were established within the creating operation budget and are retained with the handle. Reading them performs no fresh encoding or I/O.
The same supplied bytes, supported contract and finite limits produce the same structural inspection or deterministic refusal. Issuance and engine metadata can differ between containers while their portable receipt bytes remain equal.
A 1.21 artifact remains a 1.21 record. Inspection does not relabel legacy hashes, settlements or receipt fields as 2.0 identities or outcomes.
관련 규칙 · Inspect portable receipt artifacts without evaluation →결과
The declared result type is Result<Lispex.
효과
실패
Result and effects
링크Decode and validate a receipt artifact without evaluation or authentication.
Why
링크The inspection contract gives this operation one explicit input boundary and preserves the distinct result and failure cases.
Related entries
링크Inspect and validate consumer artifacts in one call
링크Inspect and validate consumer artifacts in one call
inspectConsumerArtifact accepts an admitted package, complete artifact bytes and finite host limits. It decodes and validates the receipt and evidence bindings before returning an inspection.
Inspection performs no guest evaluation or replay. Structural validity does not authenticate an issuer. authenticateEvidence applies explicit trust separately.
std.lispex exports neither verifyConsumerArtifact nor consumerArtifactFromBytes. inspectConsumerArtifact is the single artifact byte admission operation.
이유
The former verification and inspection names performed the same validation and expressed the same intention. Decoding bytes into an accepted artifact is part of that admission. Authenticating an issuer and reproducing a semantic request express different intentions.
Reject the removed verification name in a verified application
링크import std.lispex { verifyConsumerArtifact }export function main(args: Array<string>, stdin: string) -> Result<int, string> {return Ok(0)}
표준 출력 없음.기대 결과
Check this source inside an existing verified Lispex application package supplied through TOPAZ_LISPEX_APPLICATION. The product test copies that package and adds this source file. This example does not create or prepare its package lock or binary artifacts.
Diagnostics
링크Inspect portable receipt artifacts without evaluation
링크Inspect portable receipt artifacts without evaluation
inspectConsumerArtifact accepts an admitted package, complete supplied bytes and finite host limits. Validate the limits before decoding. Parse one complete artifact under its declared supported 2.0 container and codec versions.
Validate structure, integrity and supported semantic contracts. A portable receipt is required. Check that its complete request identity and canonical outcome agree with any included execution evidence and profile work binding. Reject trailing bytes, missing cores, inconsistent identities and unsupported versions.
Return an inspection containing the admitted immutable artifact, its LispexReceipt and optional LispexExecutionEvidence. artifactBytes is the byte count of the entire accepted representation. portableCoreBytes is the byte count of its portable receipt representation.
A missing execution evidence envelope is None. A validated signature envelope remains unauthenticated until authenticateEvidence accepts it under explicit trust. Structural inspection never sets an authenticated Boolean.
Invalid structure, missing portable receipt or inconsistent binding returns InvalidConsumerArtifact. Unsupported contracts or components return Admission. Exhausted host work, allocation, frame or channel budgets return LimitExceeded. The first failed check is retained without exposing a partially accepted artifact.
Inspection neither invokes the guest nor recreates a canonical outcome. It checks supplied records and cannot prove that a particular engine ran the program. Reproducing the recorded request is freshReplay and authenticating the issuer is authenticateEvidence.
consumerArtifactBytes returns the exact immutable accepted or produced container. portableCoreBytes returns its portable receipt bytes. Both representations were established within the creating operation budget and are retained with the handle. Reading them performs no fresh encoding or I/O.
The same supplied bytes, supported contract and finite limits produce the same structural inspection or deterministic refusal. Issuance and engine metadata can differ between containers while their portable receipt bytes remain equal.
A 1.21 artifact remains a 1.21 record. Inspection does not relabel legacy hashes, settlements or receipt fields as 2.0 identities or outcomes.
이유
Byte decoding and artifact validation express one admission intention, so inspectConsumerArtifact performs both. Whole artifact bytes and portable receipt bytes serve different interchange purposes. Structural inspection, issuer authentication and semantic replay preserve their separate meanings.
Validate artifact bytes and read the portable core
링크import std.bytes { Bytes }import std.lispex {LispexPackage,LispexHostLimits,LispexConsumerArtifactInspection,LispexEvidenceError,inspectConsumerArtifact,consumerArtifactBytes,portableCoreBytes,}function core(package: LispexPackage, bytes: Bytes, host: LispexHostLimits) -> Result<Bytes, LispexEvidenceError> {let result: Result<LispexConsumerArtifactInspection, LispexEvidenceError> = inspectConsumerArtifact(package, bytes, host)let inspection: LispexConsumerArtifactInspection = result?let original: Bytes = consumerArtifactBytes(inspection.artifact)let count: int = inspection.artifactByteslet coreCount: int = inspection.portableCoreBytesreturn Ok(portableCoreBytes(inspection.artifact))}function failure(error: LispexEvidenceError) -> string {return match (error) {case InvalidConsumerArtifact(report) => report.codecase Admission(report) => report.codecase Authentication(report) => report.codecase LimitExceeded(report) => report.code}}export function main(args: Array<string>, stdin: string) -> Result<int, string> {return Ok(0)}
표준 출력 없음.기대 결과
기대 결과
검사가 프로그램을 받아들입니다. 종료 코드 0.
Use a verified Lispex application package supplied through TOPAZ_LISPEX_APPLICATION. This example specifies the Lispex 2.0 behavior. The product scope remains the public 5.21.3 observation scope.