Application

DZC System Files

Overview

In AUROS, Application is the governed media type for files whose purpose is to be executed, loaded, or used to direct an application runtime—not primarily read as a document or consumed as media. File Type Master assigns six formats to this group: DLL, EXE, LNK, NODE, PYC, and WASM, all stored under DZC System Files.

What makes this group useful is format-aware inspection. AUROS records each artifact’s role, binary format, loader or runtime, target platform, parse status, and parser provenance, so compatibility and execution behavior can be understood and revalidated when a file or parser changes. DLL, EXE, and NODE are PE/COFF artifacts; LNK is a Windows Shell shortcut; PYC is CPython bytecode; and WASM is a WebAssembly module.

DZC Folder

DZC System Files

File Type Count

6 active file types

File Types

Application Available

Application — Live from Microsoft

Secure, read-only view focused directly on the Application folder.

Application-Specific Fields

These fields describe how an application artifact is interpreted, loaded, or executed. Generic facts such as filename, path, size, timestamps, and SHA-256 remain governed by File Master Primary.

Artifact Kind

Identifies the artifact's role in an application workflow: executable, shared library, native add-on, bytecode module, WebAssembly module, or shortcut. That operational role does not apply to ordinary documents or media.

Binary Format Family

Records the structured application format—such as PE, Shell Link, CPython bytecode, or WebAssembly—that determines how the file must be decoded and validated.

Runtime or Loader

Names the system responsible for loading or executing the artifact, such as the Windows loader, Windows Shell, Node.js, CPython, or a WebAssembly runtime.

Target Platform

Records the execution environment the artifact was built to target. Application compatibility depends on that environment in a way that generic file storage does not.

Parse Status

States whether the artifact's internal application structure was successfully decoded, was unsupported, or produced an error during inspection.

Parser

Identifies the application-format extractor used to inspect the artifact instead of treating it as an undifferentiated sequence of bytes.

Parser Version

Pins the extracted results to a specific parser release. Executable and runtime formats evolve, so interpretation can change when the parser changes.

Parsed UTC

Records when application metadata was extracted so it can be refreshed when the artifact changes or a newer parser becomes authoritative.