Does RabbitMQ automatic acknowledgement establish completed processing
Does RabbitMQ automatic acknowledgement establish completed processing?
In the captured RabbitMQ 4.4 guide, automatic acknowledgement considers delivery successful when sent to the connection. A worker failure can therefore lose already acknowledged deliveries before processing finishes.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not mark application work complete from automatic acknowledgement alone. Require a result bound to the delivery.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Can a replacement RabbitMQ channel acknowledge an earlier delivery tag
Can a replacement RabbitMQ channel acknowledge an earlier delivery tag?
Delivery tags are scoped to their channel. Acknowledging on another channel causes an unknown-delivery-tag exception and closes that channel.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not equate a reused numeric tag with the original delivery without channel identity.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Can RabbitMQ multiple=true acknowledge unfinished earlier deliveries
Can RabbitMQ multiple=true acknowledge unfinished earlier deliveries?
The multiple flag acknowledges every outstanding delivery tag up to and including the specified tag on that channel. It does not select only finished application tasks.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not treat a bulk acknowledgement as proof that every covered task completed. Reconcile each result.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does cancelling a RabbitMQ consumer stop or requeue in-flight work
Does cancelling a RabbitMQ consumer stop or requeue in-flight work?
Consumer cancellation prevents future dispatch but leaves previously dispatched deliveries and their acknowledgement state unchanged. Closing the channel requeues its unacknowledged deliveries.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not treat cancellation as proof of stopped side effects or recovered work. Inspect in-flight tasks separately.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does RabbitMQ expiry in one queue remove copies from other queues
Does RabbitMQ expiry in one queue remove copies from other queues?
Message TTL is independent for each queue. A routed message can expire at different times, and expiry in one queue does not affect its copies elsewhere.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not infer system-wide removal or cancellation from one queue expiry. Account for routed copies and delivered tasks.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does RabbitMQ redelivered=true prove a previous business action
Does RabbitMQ redelivered=true prove a previous business action?
The redelivered flag is a hint of prior delivery. The original delivery may never have reached a consumer, so it does not establish processing or a completed external effect.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not discard work as completed solely from the flag. Require operation-level results or deduplication evidence.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Is Service Bus session state removed after consuming every message
Is Service Bus session state removed after consuming every message?
Session state remains until explicitly cleared, even after all messages are consumed. Microsoft advises clearing retained state when processing finishes.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not equate an empty session with erased workflow state or completed cleanup.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does resubmitting a Service Bus dead letter restore its session position
Does resubmitting a Service Bus dead letter restore its session position?
Resubmission receives a new enqueue time and sequence number, losing the original ordering relative to other session messages.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not assume original order is restored. Reconcile dependencies and completed effects before replay.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does a Service Bus transaction roll back external database or API effects
Does a Service Bus transaction roll back external database or API effects?
Downstream databases and services do not automatically participate in the Service Bus transaction scope. Broker rollback does not establish their outcome.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Refuse an all-or-nothing business outcome without independent external-effect evidence.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does Service Bus automatically retry exceptions inside a transaction
Does Service Bus automatically retry exceptions inside a transaction?
The documented transaction behavior does not retry an operation after an exception within the transaction scope. Recovery must account for the transaction and separate effects.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not assume retry settings repaired transactional work. Require a recorded recovery result.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does a Service Bus scheduled sequence number survive activation
Does a Service Bus scheduled sequence number survive activation?
The scheduled sequence number is valid only while scheduled. Activation enqueues the message with a new sequence number.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not join scheduled and active records solely by the old sequence number. Preserve a separate correlation identity.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Can Service Bus activate a scheduled message while cancellation occurs
Can Service Bus activate a scheduled message while cancellation occurs?
Activation and cancellation are independent operations without mutual locking. Cancellation during activation does not reverse activation, and the message can still become active.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not promise stopped execution from near-deadline cancellation. Reconcile activation and worker outcomes.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Will TTL clear messages already in a Service Bus dead-letter queue
Will TTL clear messages already in a Service Bus dead-letter queue?
Time-to-live is not observed inside the dead-letter queue. There is no automatic cleanup; dead letters remain until explicitly retrieved and completed.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not use original TTL as disposal evidence. Verify the relevant inventory and completion records.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does Pub/Sub maxDeliveryAttempts enforce an exact retry ceiling
Does Pub/Sub maxDeliveryAttempts enforce an exact retry ceiling?
Counting requires correct dead-letter configuration and IAM permissions. Forwarding is best effort, counts can reset, and deliveries may exceed the configured maximum.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not treat the setting as a hard execution cap. Check actual attempts and operation-level idempotency.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does Pub/Sub dead-letter forwarding preserve the original envelope unchanged
Does Pub/Sub dead-letter forwarding preserve the original envelope unchanged?
Pub/Sub wraps an undeliverable message in a new message and adds attributes identifying the source subscription before forwarding it.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not discard original-message and source-subscription context during reconstruction.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does every Pub/Sub snapshot provide seven new days of recovery
Does every Pub/Sub snapshot provide seven new days of recovery?
Snapshot lifetime is seven days minus the oldest unacknowledged message age. A snapshot expiring in less than one hour cannot be created.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not approve rollback coverage from creation time alone. Verify backlog age and actual expiration.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does successful Pub/Sub seek instantly change all delivered messages
Does successful Pub/Sub seek instantly change all delivered messages?
Seek guarantees eventual delivery of messages made unacknowledged, but delivery does not change instantly. Messages outside the target state can arrive while seek takes effect.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not infer failed seek or safely repeat an effect solely from immediate deliveries. Reconcile identities and prior results.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Can Pub/Sub replay acknowledged messages without retained history
Can Pub/Sub replay acknowledged messages without retained history?
Time-based replay of acknowledged messages requires topic retention or subscription retention of acknowledged messages. A timestamp alone does not create retained history.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not promise recovery beyond retained data. Verify retention and the eligible interval.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does an OCI artifactType query prove the response was filtered
Does an OCI artifactType query prove the response was filtered?
Filtering support is recommended rather than universal. Applied filtering must be reported in OCI-Filters-Applied.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not classify every descriptor from the query alone. Inspect applied-filter evidence and returned types.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does a referrers API 404 prove no OCI evidence exists
Does a referrers API 404 prove no OCI evidence exists?
Distribution 1.1.1 requires referrers tag-schema fallback after a referrers API 404. API failure alone is not completed discovery.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not report absent signatures or SBOMs before evaluating the fallback result.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does OCI referrer discovery cover every repository containing a digest
Does OCI referrer discovery cover every repository containing a digest?
The 1.1.1 response lists matching subject references within the requested repository namespace. It is not a global cross-repository inventory.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not infer global absence from one namespace. Record searched evidence locations.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does deleting an OCI tag remove its manifest and every alias
Does deleting an OCI tag remove its manifest and every alias?
Tag deletion makes that tag return 404. Manifest deletion by digest makes the digest and tags pointing to it return 404.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not treat tag removal as proof of erasure, cache eviction or cross-repository revocation.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does a valid OCI descriptor establish trustworthy downloaded content
Does a valid OCI descriptor establish trustworthy downloaded content?
Image 1.1.1 recommends checking size and digest before consuming untrusted content. A size mismatch should prevent trust; valid descriptor syntax does not establish matching bytes.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Refuse content identity without consistent checks. A matching digest does not establish publisher authority or safety.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Is embedded OCI descriptor data exempt from content verification
Is embedded OCI descriptor data exempt from content verification?
The Base64 data field must contain the referenced content. Image 1.1.1 recommends checking decoded bytes against digest and size.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not bypass validation for inline data or treat encoding as integrity evidence.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does a valid OCI image index guarantee a usable image
Does a valid OCI image index guarantee a usable image?
Image 1.1.1 requires the manifests array but permits it to be empty. Validity does not establish an available platform manifest.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not approve deployment from parsing alone. Require a compatible manifest and verified content.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does an OCI subject field approve the referenced artifact
Does an OCI subject field approve the referenced artifact?
Image 1.1.1 defines subject as a weak association used for referrer discovery. It does not define certification or approval.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not treat attachment association as trusted approval. Verify evidence and acceptance policy separately.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does a Notary policy pass mean every signature check passed
Does a Notary policy pass mean every signature check passed?
The pinned specification distinguishes strict, permissive, audit and skip. Logged failures need not reject an artifact; skip performs no signature verification.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not report full verification without the effective level and individual outcomes.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does the Notary strict label establish the effective verification policy
Does the Notary strict label establish the effective verification policy?
Custom overrides can change authenticity, timestamp, expiry and revocation validation. Integrity cannot be overridden, and skip cannot be customised.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Inspect effective overrides and implementation version rather than accepting the level name alone.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does a global Notary policy govern every artifact repository
Does a global Notary policy govern every artifact repository?
For OCI artifacts, an exact repository policy takes precedence over a global rule. Without either match verification must fail; URIs must be fully qualified.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Resolve the exact repository and selected policy before asserting effective requirements.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does Notary trustedIdentities=* select a particular builder
Does Notary trustedIdentities=* select a particular builder?
The wildcard trusts signing identities issued by configured trusted authorities. It does not select one expected certificate subject.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not infer a specific builder from wildcard acceptance. Require explicit identity evidence and approved trust stores.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does Notary artifact success validate every attached signature
Does Notary artifact success validate every attached signature?
The pinned OCI workflow can skip failed candidates and accept a policy-valid signature with matching signed digest and requested annotations.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not report all signatures as validated from overall success. Retain the accepted signature and findings.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does Notation policy import merely add a rule to existing configuration
Does Notation policy import merely add a rule to existing configuration?
The documented import example replaces the active trust policy after confirmation. Showing the policy afterwards confirms the resulting configuration.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not assume a merge or preserved requirements. Compare before and after and retain a restoration copy.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Where does Service Bus retain a message that cannot be forwarded
Where does Service Bus retain a message that cannot be forwarded?
For failed auto-forward or send-via transfer, the message is placed in the transfer dead-letter queue of the source entity that forwarded it, not the intended destination.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not declare the transfer lost or recovered from the destination inventory alone. Inspect the source transfer DLQ and reconcile actual effects.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does OCI cross-repository mount HTTP 202 mean the blob is available
Does OCI cross-repository mount HTTP 202 mean the blob is available?
A successful mount returns 201 Created. If mounting is unsupported or cannot be performed, 202 indicates an upload session has begun and the client may upload the blob.
Documentation reviewed 2026-10-29. Primary source.
Boundaries
- Do not treat 202 as completed blob placement. Require successful mount or completed upload evidence before accepting distribution completeness.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review