aiko-dsh-bid-studio
v0.2.4
Published
Installable Bid Studio workbench for DeepSeek Harness, powered by the Aiko Ontology Kernel.
Maintainers
Readme
Aiko DSH Bid Studio
An installable DeepSeek Harness business application that contributes:
- a Bid Studio entry in the official desktop application sidebar;
- a complete tender ontology with object, relationship, Function, and Action definitions;
- a durable local execution route from tender intake to human review and export;
- an ontology inspector that renders every definition category and workflow step.
Bid Studio is a scene plugin built on the independently installed Aiko DSH Ontology Kernel. It contributes only the bid.* definition, executable adapters, tools, workflow, and workbench. The shared Kernel owns the ontology runtime, durable graph storage, and browser remotes so future contract and project workbenches can reuse one provider.
Install through the market
This plugin targets the official DSH 0.1.5-alpha.2 client APIs. In the Electron application with aiko-dsh-market installed, select aiko-dsh-bid-studio from the organization catalog and confirm installation. The market installs a compatible Ontology Kernel first and activates both packages together. Navigation, workbench styles, the ontology inspector, and client remotes ship in this plugin's browser artifact.
The desktop-enabled market requires its accompanying desktop bridge; the unmodified upstream release does not expose that API. Candidate release URLs become usable after publication.
Install from npm on Web
dsh plugin --profile web add [email protected] [email protected]
dsh --profile web --dump-config
dsh --profile webRelease tarballs contain built host and browser artifacts under lib/. Run pnpm install, pnpm run build, and pnpm test to develop the independent plugin; npm pack builds the publishable tarball.
After the profile restarts, open 投标工作台 from the application sidebar. The current demo implementation persists projects and graph records locally, runs deterministic Action adapters in order, pauses for human approval, and exports a reviewable Markdown artifact. The plugin owns this sequencing and records run and step state through the Ontology Kernel. It does not require an active chat Agent or replace the upstream workflow provider. AI-driven Action adapters remain an extension point of the Ontology Kernel.
Install the Kernel only once per profile. Multiple scene plugins can register independent namespaces such as bid.* and contract.* against that single runtime. The Aiko catalog-aware market installs required platform plugins automatically.
Source provenance
The initial implementation was extracted from the public packages/business/bid-studio and packages/bundle/bid-studio packages in qwe8652591/deepseek-harness at commit 8bca1e10fc2066e18309cd5fc5a62bd69b78de13. This independent repository owns distribution and client integration. The Harness application does not embed the business package.
Distribution
Active development lives in the private aiko-dsh-plugins/dsh-bid-studio-source repository. Publish a checked tarball with npm publish ./aiko-dsh-bid-studio-0.2.4.tgz --access public --tag latest --registry=https://registry.npmjs.org/. Packages contain runtime JavaScript and declarations without the src tree. The aiko-dsh-plugin-catalog package lists package names. This plugin publishes its own guides and previews in npm metadata. The updated desktop installer repairs retired Aiko GitHub sources in one transaction; private source commits stay private.
License
MIT
Market metadata and compatibility
Edit market/metadata.json, market/en.md, market/zh.md and local PNG resources, then run npm run build:metadata. The generated dsh.market fields ship in the npm manifest, so browsing help does not download the runtime archive. dsh.compatibility.host declares the exact tested Aiko DSH release, currently 0.1.5-alpha.2; the updated desktop installer checks it before activation. Expand this declaration only after testing the supported releases. Plugin upgrades require only a new plugin publication; the names-only directory changes only when adding or removing plugins.
