Bruno Postle
f864004e0a
The repo outgrew a single-project layout: the reusable form-language template and the draft paper about the method were mixed in with Ecuador-specific ref/narratives/docs, and a second real project (Harbor House) had been growing inside templates/examples/ despite no longer being just a template demo. Split into: - method/ - the generalized form-language prompt template and the paper about the method, project-agnostic - projects/ecuador-museum/ - the original counter-proposal (ref/, narratives/, docs/, unchanged in content) - projects/harbor-house/ - promoted out of templates/examples/, now a peer project with its own ref/narratives/docs, including previously untracked pattern subset, narrative, and illustration material Root CLAUDE.md now covers the shared method and repo-wide conventions; each project gets its own CLAUDE.md with project-specific brief, inputs, and status. Updated all internal path references (paper.md, outline.md, per-project CLAUDE.md, settings.local.json). Dropped stray scratch files superseded by proper copies (all.txt, the already- converted pattern-language PDF). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
75 lines
No EOL
2.6 KiB
Text
75 lines
No EOL
2.6 KiB
Text
GUIDE FOR THE SUBMISSION OF THE ENABLING DOCUMENTATION FOR
|
||
STAGE 1
|
||
To ensure the correct submission of the Stage 1 enabling documentation, you must follow this
|
||
procedure for consolidating and remitting information via email:
|
||
1.
|
||
|
||
Consolidation of Documentation
|
||
•
|
||
•
|
||
|
||
2.
|
||
|
||
Single File: All supporting documentation (annexes, portfolio, CVs and certificates)
|
||
must be contained in a single compressed file in .ZIP format.
|
||
Formats: The documents inside the compressed file must be presented in digital PDF
|
||
format. The graphic sheet for each work or project presented must be in DIN A3
|
||
format.
|
||
Cloud Upload & Access
|
||
|
||
•
|
||
•
|
||
•
|
||
3.
|
||
|
||
External Platform: The .ZIP file must be uploaded to a cloud storage platform (such as
|
||
Google Drive, OneDrive, Dropbox, or similar).
|
||
Access Permissions: The download link must be configured with public read
|
||
permissions to ensure immediate access by the Evaluation Committee.
|
||
Email Attachments Restriction: Do not attach files directly to the email.
|
||
MD5 Hash Code Generation and Incorporation
|
||
|
||
To guarantee data integrity and ensure the file has not been altered after sending, the use of
|
||
a verification code is required:
|
||
•
|
||
|
||
•
|
||
|
||
•
|
||
|
||
Nature of Hash: The MD5 Hash is a unique alphanumeric code generated from your
|
||
final .ZIP file. It is not an additional file, but a string of text to validate the integrity of
|
||
the information.
|
||
Tools to Generate it: You can generate it using system commands (e.g. certutil -hashfile
|
||
on Windows or md5 on macOS) or MD5 HASH generation applications (e.g. QuickHash
|
||
GUI, HashMyFiles, WinMD5Free, etc.)
|
||
Once the HASH has been generated, this code must be included in the body of the
|
||
application email.
|
||
|
||
4.
|
||
|
||
Mail Delivery Protocol (Conforming to Annex 3)
|
||
|
||
To: convocatoria@museonacional.gob.ec
|
||
Subject: "Credential and Portfolio Delivery - Stage 1 - [Team Name]".
|
||
Body Contents:
|
||
I hereby submit the enabling documentation, credentials, and portfolio corresponding to Stage
|
||
1 of the Open Call for Architectural schematic design proposals for the New Building of the
|
||
National Museum of Ecuador.
|
||
I act as Project Director and representative of the applicant team [Team Name, if applicable],
|
||
in compliance with the requirements established in the technical bases, including all
|
||
documenta- tion duly signed and submitted in digital format.
|
||
The enabling documentation, annexes, and portfolio can be accessed at the following link:
|
||
[Link to download documents in ZIP format]
|
||
[Hash Code]
|
||
|
||
I would like to confirm receipt of these documents.
|
||
I remain attentive to any additional communication related to the process.
|
||
|
||
Cordially,
|
||
[Name of Project Director] [Professional Title]
|
||
[Phone]
|
||
[Email]
|
||
[Name of Team/Studio/Firm]
|
||
|
||
|