Penghou.IO.Abstractions 0.1.0-preview.3

This is a prerelease version of Penghou.IO.Abstractions.
dotnet add package Penghou.IO.Abstractions --version 0.1.0-preview.3
                    
NuGet\Install-Package Penghou.IO.Abstractions -Version 0.1.0-preview.3
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Penghou.IO.Abstractions" Version="0.1.0-preview.3" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Penghou.IO.Abstractions" Version="0.1.0-preview.3" />
                    
Directory.Packages.props
<PackageReference Include="Penghou.IO.Abstractions" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Penghou.IO.Abstractions --version 0.1.0-preview.3
                    
#r "nuget: Penghou.IO.Abstractions, 0.1.0-preview.3"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Penghou.IO.Abstractions@0.1.0-preview.3
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Penghou.IO.Abstractions&version=0.1.0-preview.3&prerelease
                    
Install as a Cake Addin
#tool nuget:?package=Penghou.IO.Abstractions&version=0.1.0-preview.3&prerelease
                    
Install as a Cake Tool

Penghou shared contracts and providers

This repository owns domain-named, replaceable contracts such as Penghou.IO.Abstractions and Penghou.Workflow.Abstractions. Product implementations consume these contracts. Zhinu implements workflow execution; Hufu.Workflow implements optional workflow authorization; another engine or authority implementation can use the same neutral boundary.

The workflow contract plan defines the package's ownership, bounds and delivery order. WA-1/2/3 are complete: Penghou.Workflow.Abstractions 0.1.0-preview.2 is published and qualified. See the contract manual, source/design review, release checkpoint and public-package qualification. Zhinu's exact published-package source adoption and ZA-3A/3B/4 runtime qualification are complete locally; the unchanged preview.15 compatibility suite also passed on .NET 8/10. The next step is passing remote CI and user-run ZA-6 publication of Zhinu 0.2.0-preview.1 with remote CI. Hufu HA-1/2/3 remains held until that publication; Luban LW-1 is optional and independent. See the adoption checkpoint.

It supplies IExecutionAuthorizer and immutable execution identity, context, requirement and result values. It has no dependency on IO, Zhinu or Hufu, and ships no engine, policy evaluator or default authorizer. CI tests the contracts on .NET 8/10 and Linux/Windows, inspects the package and proves package-only consumption. The earlier input-free Publish to NuGet workflow published this package from main; existing IO versions were not republished. Exact public package contents match CI apart from the repository signature, and fresh-cache NuGet-only consumers pass on .NET 8 and .NET 10. This qualifies the package boundary, not Zhinu or Hufu runtime behavior.

Governable model and HTTP transports

New candidates Penghou.Model.Abstractions and Penghou.Http.Abstractions at 0.1.0-preview.1 define independent, product-neutral execution seams. They contain no Baize, Hufu, provider SDK, workflow, policy or credential implementation. Model transports carry typed data plus provider/model/endpoint, context and usage; HTTP supports bounded binary/multipart requests and owned response chunks.

See the contract manual, ADR 0004, consumer closure matrix and release checkpoint. Model invocation and arbitrary HTTP remain distinct capabilities. Contract qualification does not prove consumer authority, credential containment or network isolation.

The input-free Publish transport abstractions to NuGet workflow on main now targets only these two packages. Existing IO/workflow versions remain immutable; their build/test/package profiles stay regression checks. Publish the new contracts and verify indexing before Baize adoption, then implement Hufu's optional enforcement adapters. Remote CI/publication status is in the checkpoint; a local candidate is not a published package.

Penghou I/O

Penghou I/O supplies bounded resource capabilities for AI tool usage, with explicit authorization at each concrete resource boundary. Trusted hosts inject providers and authority implementations; Hufu is an optional integration.

Architecture direction (2026-10-02): replaceable resource capabilities, with the original specification, public-type inventory and corrective roadmap. ADR 0003 records the implemented correction. The delivery plan and handoff distinguish qualification, publication and consumer adoption.

Three .NET 8 and .NET 10 NuGet package candidates share version 0.1.0-preview.1; publication status is recorded in the delivery plan.

  • Penghou.IO.Abstractions contains the neutral request, result, provider and authorization contracts. It has no provider or protocol implementation dependency.
  • Penghou.IO.Protocols contains the versioned request identity codec and the Windows workspace path profile. It depends on the neutral contracts package.
  • Penghou.IO.Local contains the Windows filesystem provider and depends on both the contracts and protocol packages. It applies host-supplied authorization and mutation-journal checks at the concrete resource boundary.

Build and test both target frameworks, with the native Windows provider qualified on Windows. See the release guide for manual publication from the checked-in version or a matching release tag.

Every operation carries a host-authenticated HostInvocation with subject, effect, attempt, scope references, and request identity. These records are data only: contracts do not authenticate host IDs or enforce checks. The host composition authenticates the operation and its scope; the provider snapshots inputs and makes the final current-authority check for each concrete action and resource. There is no ambient-user lookup or default permit. A WorkspacePath reference describes provenance; it does not grant permission.

Luban validates its whole pipeline's syntax, types, and execution profile before I/O. Luban owns semantic typed effects and finite dataflow; Fuwen and Zhinu own workflow control and durability. Preflight checks all nodes' known static effects and exact targets, rejecting a known denied write before upstream reads or artifacts. This advisory check reserves no authority and does not replace provider access checks. Dynamic targets require bounded, authorized discovery. An ls list effect, a later gc read effect, and a write each require their own check. A live denial can follow earlier reads, but the denied write must not occur. There is no global pipeline atomicity; intermediates use finite buffered values with byte/work bounds and cancellation; lazy production and backpressure are not guaranteed. Persistence and debug/release artifacts require explicit authorization.

ADR 0002 adds the planned preview resolution and commit barrier: authorized discovery resolves dynamic mutation targets, the complete known mutation set is admitted before writes begin, and every actual I/O still receives live checks. WhatIf leaves opaque tools unexecuted. Luban now implements a separate programmatic capture-only WhatIf profile using this reader; its plans cannot commit and WhatIf never dispatches the separate executor. Luban's single and batch patch executors require explicit host admission, live resource checks and journaled start/completion evidence. Luban materializes the exact text edits; Local conditionally persists frozen bytes. Batch execution is ordered and can leave a completed prefix; it is not an atomic transaction. Production mutation-host composition and terminal-outcome recovery remain separate qualification obligations.

See architecture, provider contract, the roadmap, and decision 0001. The Apache-2.0 license applies.

The implementation plan records the Windows read/list provider and Luban's read migration. See its qualified profile, identity encoding, and the separate Local conditional existing-file write profile. Other mutations and the web backend remain pending.

Build with the .NET 10 SDK:

dotnet test Penghou.IO.slnx -c Release -f net8.0
dotnet test Penghou.IO.slnx -c Release -f net10.0

CI runs these Windows tests, builds the neutral contracts and protocols on Linux, packs all three packages, verifies their identities and contents, and restores a separate package-only consumer from the generated local feed. CI packages use a unique prerelease version and are not published.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (3)

Showing the top 3 NuGet packages that depend on Penghou.IO.Abstractions:

Package Downloads
Penghou.Hufu.IO

Optional Hufu authority enforcement for neutral Penghou IO providers.

Penghou.Luban

Authorization-aware language and bounded runtime for secure AI tool usage, with provider-neutral file operations and deterministic text changes.

Penghou.IO.Local

Bounded local filesystem provider for Penghou resource I/O contracts.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.1.0-preview.3 79 10/13/2026
0.1.0-preview.2 81 10/13/2026
0.1.0-preview.1 959 10/3/2026