SHIRO & Co.

KOSUKE PROTOCOL

PRESS DEMONSTRATION / 2026

SHIRO & Co. · Kosuke Protocol Applied Workflow

Observation to Proposal

Observation to Proposal

Observation to Proposal

A supervised handoff from structural observation to proposal development.

A supervised handoff from structural observation to proposal development.

Observation does not automatically become action.

Observation does not automatically become action.

Structural handoff does not authorize external use.

SHIRO & Co. has implemented an explicit handoff from structural observation into proposal development, with provenance, permission and uncertainty preserved before human review. The system transfers structure, not people.

OBSERVE

HANDOFF BOUNDARY

INTERPRET

PROPOSAL BOUNDARY

HUMAN REVIEW

PROPOSED NEXT ACTION

Structure moves forward. Personal contact data does not need to.

PRESS DEMONSTRATION

This page presents a controlled press demonstration of SHIRO & Co.’s Observation-to-Proposal workflow. The live production interfaces are not publicly accessible from this page. For media inquiries or information about this implementation, please contact SHIRO & Co.

IMPLEMENTED CONNECTION

The Observatory now has an explicit handoff into proposal development.

The Observatory now has an explicit handoff into proposal development.

A user can select a structural observation from an Observatory detail page and send that structure into the proposal workflow. The handoff is explicit. It is not automatic. The Observatory remains an observation system.

The handoff can include observation identity, source facts, structural change, transformation pattern, region, provenance, usage cautions, and distinctions between fact and interpretation. It does not display private contact fields.

CONTACT DATA OBSERVATORY

Observe transformation

SEND STRUCTURE TO PROPOSAL

HANDOFF BOUNDARY

ALLOW — STRUCTURAL CONTEXT ONLY / HOLD / DENY

INTERPRET FOR A SELECTED COMPANY

PROPOSAL BOUNDARY

ALLOW / HOLD / DENY

HUMAN REVIEW

PROPOSED NEXT ACTION

The handoff transfers structure, not personal contact data.

The handoff transfers structure, not personal contact data.

The system is designed so that proposal reasoning can receive the structural meaning of an observation without requiring personal contact information.

A company appearing in an Observatory is not automatically a sales target.

We are moving a structure across the boundary, not a person.

NOT

Personal contact data · Contact enrichment · Personal profiles · Automatic proposal approval · External action

YES

Observation ID · Source fact · Structural change · Provenance · Usage caution · Interpretive boundary

The Observatory stays observational.

The Observatory stays observational.

HANDOFF BOUNDARY

May this observed structure enter the proposal system?

ALLOW — STRUCTURAL CONTEXT ONLY

The observed structural pattern may move forward as interpretive context.

HOLD

The structure remains unresolved until review or verification is complete.

DENY

The observed structure does not enter proposal interpretation.

It does not authorize:

personal contact transfer · contact enrichment · use of personal profiles · automatic proposal approval · external action

SUPERVISORY GATE

TWO BOUNDARIES BETWEEN OBSERVATION AND ACTION

TWO BOUNDARIES BETWEEN OBSERVATION AND ACTION

The Handoff Boundary determines whether an observed structure may enter the proposal system. The Proposal Boundary is applied after a target company, business concern and relevant signals have been identified. It evaluates whether the emerging proposal is sufficiently grounded, relevant to the selected company and appropriate to proceed toward external use.

HANDOFF BOUNDARY

May this observed structure enter the proposal system?

ALLOW — STRUCTURAL CONTEXT ONLY

ALLOW — STRUCTURAL CONTEXT ONLY means that the observed structural pattern may move forward as interpretive context. It does not authorize transfer of personal contact data, contact enrichment, use of personal profiles, automatic proposal approval, or external action.

PROPOSAL BOUNDARY

After interpretation for a selected company, may the emerging proposal proceed toward external use?

ALLOW / HOLD / DENY

HOLD does not automatically become ALLOW.

ALLOW

Information is sufficiently grounded and permitted to continue into interpretation.

HOLD

Information may be relevant, but one or more conditions remain unresolved.

DENY

The affected information is excluded from downstream proposal use.

The boundaries evaluate more than relevance.

The boundaries evaluate more than relevance.

SOURCE — Where did the information come from?

IDENTITY — Is attribution sufficiently grounded?

PERMISSION — Is there a valid basis for use?

FACT VERSUS INFERENCE — Stated, observed or inferred?

PROVENANCE — Can it be traced back?

SCOPE — Is it relevant here?

SENSITIVITY — Should it be excluded?

PAYLOAD VALIDITY — Is the public structural input valid?

This is a supervisory model, not legal certification.

UNRESOLVED CONDITIONS

Not everything should immediately become ALLOW or DENY.

Not everything should immediately become ALLOW or DENY.

HOLD prevents information from proceeding while required conditions remain unresolved. Possible HOLD conditions include uncertain company attribution, unresolved customer identity, unconfirmed inference, incomplete provenance, unclear permission, conflict between a customer statement and an external source, sensitive information, or missing context.

HOLD → CONDITION RESOLVED → ALLOW

HOLD → REVIEW / VERIFICATION → ALLOW / DENY / REMAIN ON HOLD

Uncertainty is preserved instead of silently converted into confidence.

Uncertainty is preserved instead of silently converted into confidence.

TRACEABILITY

Source context remains attached.

Source context remains attached.

Provenance is preserved as typed source information rather than flattened into undifferentiated text.

PRIMARY SOURCE FACTS

OBSERVATORY OBSERVATIONS

SYSTEM INTERPRETATIONS

TRACEABLE CONTEXT

Proposal-facing labels include CUSTOMER STATED, SALES OBSERVED, PUBLIC SOURCE, OBSERVATORY STRUCTURE and SYSTEM INFERENCE.

An inference should not be presented as a customer statement.

An inference should not be presented as a customer statement.

Before a Micro Proposal is produced, information is separated by what it actually is.

Before a Micro Proposal is produced, information is separated by what it actually is.

WHAT WAS STATED — Information directly expressed by the customer.

WHAT WAS OBSERVED — Information recorded by a sales, consulting or field team.

WHAT WE INFER — Interpretation generated from context.

WHAT MUST BE VERIFIED — Potentially relevant information requiring confirmation.

WHAT MUST NOT BE USED — Information excluded by permission, provenance, relevance or certainty concerns.

DOWNSTREAM INTERPRETATION

Two proposal entry points remain.

Two proposal entry points remain.

Signal to Proposal

External change → Structure → Meaning → Opportunity → Proposal

What changed outside the company, and what could that mean here?

Customer to Proposal

Customer context → Classification → Meaning → Opportunity → Micro Proposal

What did this customer reveal, and what could that mean next?

Observatory structure can enter either path only through explicit user action.

Context keeps its identity.

Context keeps its identity.

OBSERVATORY STRUCTURE ≠ CUSTOMER FACT

OBSERVATORY STRUCTURE ≠ CUSTOMER FACT

Structural context from the Observatory can inform interpretation, but it must remain distinguishable from information directly stated by a customer. This distinction is retained during proposal preparation and human review.

FINAL RESPONSIBILITY

Proposal output still requires a human decision.

Proposal output still requires a human decision.

Before final export, reviewers can inspect the proposal hypothesis, supporting inputs, provenance, stated / observed / inferred distinctions, HOLD items, excluded information and unresolved verification items. External submission is not automatic. Presentation export is available only after approval.

APPROVE

RETURN FOR REVISION

KEEP ON HOLD

REJECT

“An observation should not become an action simply because a system can generate one.” — Kosuke Shirako, Founder, SHIRO & Co.

“An observation should not become an action simply because a system can generate one.” — Kosuke Shirako, Founder, SHIRO & Co.

CONTACT DATA OBSERVATORY

EXPLICIT HANDOFF

HANDOFF BOUNDARY — ALLOW — STRUCTURAL CONTEXT ONLY / HOLD / DENY

INTERPRET

PROPOSAL BOUNDARY — ALLOW / HOLD / DENY

HUMAN REVIEW → PROPOSED NEXT ACTION

Observation does not automatically become action.

Observation does not automatically become action.

ALLOWING A STRUCTURE INTO INTERPRETATION IS NOT THE SAME AS ALLOWING A PROPOSAL INTO EXTERNAL USE.

SHARED FOUNDATION

An applied Kosuke Protocol workflow.

An applied Kosuke Protocol workflow.

The new implementation adds two explicit supervisory boundaries between observation and proposed action: first, a Handoff Boundary determines whether observed structure may enter interpretation; then a Proposal Boundary evaluates whether an emerging proposal may proceed toward external use. Final responsibility remains with a human reviewer.

FRAGMENT

OBSERVATION

CONNECTION

MEANING

FORM

RELATED CONCEPT

The same HOLD principle appears across SHIRO & Co.’s supervisory work.

The same HOLD principle appears across SHIRO & Co.’s supervisory work.

The Proposal Boundary uses HOLD as a state for unresolved conditions. This connects conceptually with The Supervisory Layer, where HOLD describes a formal supervisory state between proceeding and rejecting.

The workflow is intentionally not fully automatic.

The workflow is intentionally not fully automatic.

No automatic Observatory ingestion. No automatic personal-contact transfer. No automatic conversion of inference into fact. No automatic HOLD-to-ALLOW transition. No automatic external proposal submission. No removal of human review.

Automation stops at the boundary where judgment remains necessary.

Automation stops at the boundary where judgment remains necessary.

CONTROLLED DISCLOSURE

What this press page shows — and what it does not.

What this press page shows — and what it does not.

SHOWS — workflow concept, explicit handoff, Handoff Boundary, Proposal Boundary, ALLOW / HOLD / DENY, provenance model, information classification and Human Review.

DOES NOT SHOW — live production interfaces, internal implementation details, private reasoning methods, private configurations, or company-specific knowledge bases.

This page presents a press demonstration of SHIRO & Co.’s observation-to-proposal workflow. The live production interfaces are not publicly accessible from this page.

Press visuals

Observation → Handoff Boundary → Interpretation → Proposal Boundary → Human Review

Observation → Handoff Boundary → Interpretation → Proposal Boundary → Human Review

An explicit handoff moves structural observation into proposal development while keeping two separate decisions: whether the structure may enter the system and whether the resulting proposal may proceed.

ALLOW — STRUCTURAL CONTEXT ONLY

The Handoff Boundary may allow structural context to move forward without authorizing personal-contact transfer, enrichment or any later proposal.

ALLOW / HOLD / DENY

The Proposal Boundary determines whether an emerging proposal may proceed, must remain on HOLD, or should be excluded from external use.

Neutral placeholders for real diagrams or screenshots. No screenshots have been fabricated.

About SHIRO & Co.

SHIRO & Co. is an independent Observation & Protocol Studio based in Tokyo. The company studies structural change across society, markets, technology and everyday human activity and develops systems, frameworks and applied forms from those observations. Its shared foundation is the Kosuke Protocol.

For media inquiries and implementation information

For media inquiries and implementation information

For media inquiries or information about this implementation, please contact SHIRO & Co.

SHIRO & Co.

Observation to Proposal

Kosuke Protocol

Press Demonstration / 2026

© 2026 SHIRO & Co.